How to scan avalible wireless (802.11b) network in a MFC program?
-
Does anybody know how to scan avalible wireless (802.11b) network in a MFC program? Any tips will be appreicated! mao
-
Does anybody know how to scan avalible wireless (802.11b) network in a MFC program? Any tips will be appreicated! mao
What do you mean by "scan wireless network?"
-
What do you mean by "scan wireless network?"
What "scan wireless network" means enum all avalible 802.11b wireless network on air. Sometime, there are more than one AP (access point) or Adhoc network avalible on air. I want to enum all the avalible network and then let user choose to connect one of them. DavidCrow wrote: What do you mean by "scan wireless network?"
-
What "scan wireless network" means enum all avalible 802.11b wireless network on air. Sometime, there are more than one AP (access point) or Adhoc network avalible on air. I want to enum all the avalible network and then let user choose to connect one of them. DavidCrow wrote: What do you mean by "scan wireless network?"
Take a look at the DDK documentation for 802_11 OIDs. For example, an application can send OID_802_11_SCAN_LIST to ask the miniport driver to do active or passive scan. This list is then returned to the application. User Mode applications cannot send OIDs directly to the miniport therefore you have to have a protocol driver in between to do this correctly. On Xp the zero config service uses a variation of "User Mode I/O" protocol driver (in the DDK Samples) to send these OIDs. Some vendors implement private IOCTL codes in the miniport, in that case application can just send IOCTLs directly to the miniport. :omg:
-
Take a look at the DDK documentation for 802_11 OIDs. For example, an application can send OID_802_11_SCAN_LIST to ask the miniport driver to do active or passive scan. This list is then returned to the application. User Mode applications cannot send OIDs directly to the miniport therefore you have to have a protocol driver in between to do this correctly. On Xp the zero config service uses a variation of "User Mode I/O" protocol driver (in the DDK Samples) to send these OIDs. Some vendors implement private IOCTL codes in the miniport, in that case application can just send IOCTLs directly to the miniport. :omg:
thank you very much, it sounds ok, i will try this way.
-
Take a look at the DDK documentation for 802_11 OIDs. For example, an application can send OID_802_11_SCAN_LIST to ask the miniport driver to do active or passive scan. This list is then returned to the application. User Mode applications cannot send OIDs directly to the miniport therefore you have to have a protocol driver in between to do this correctly. On Xp the zero config service uses a variation of "User Mode I/O" protocol driver (in the DDK Samples) to send these OIDs. Some vendors implement private IOCTL codes in the miniport, in that case application can just send IOCTLs directly to the miniport. :omg:
Thank you very much for your help. After I studied some DDK documents, I relized you r a real expert in this area! Since WinXP introduced a WZC service, does this mean in an XP box, I needn't write a NDISUIO driver myself, instead I can use WZC to do everything I want? However I searched MS site and found very few information on WZC, almost get no information on how to use WZC service at all. Could you give me more tips? Thanks so!