Re: Wi-Fi AP selection by BSSID
- From: "Benoît Bousquet" <bbousquet@xxxxxxxxxxxxxxxx>
- Date: Thu, 6 Oct 2005 13:43:57 -0400
Further evidence confirming the issue: updating Intel 2200BG integrated
wireless adapter drivers from the 2004 (8.something) version to the 2005
(9.0.something) version magically solved the issue with those adapters.
-BB
"Benoît Bousquet" <bbousquet@xxxxxxxxxxxxxxxx> wrote in message
news:uwojtXpyFHA.3952@xxxxxxxxxxxxxxxxxxxxxxx
> That's what I was beginning to believe. So far I tested a number of
> different adapters (DLink DWL-122 USB, Cisco Aironet 350 PCMCIA, DLink
> AirPlus DWL-650 PCMCIA, some Sony Ericsson GPRS/WiFi PCMCIA cards, USR
> 802.11g Turbo-Something PCMCIA, LinkSys 802.11b WiFi USB) and only the
> LinkSys USB card behaved properly.
>
> -BB
>
> "Pavel A." <pavel_a@xxxxxxxxxxxxxxx> wrote in message
> news:5D4EC7D5-AFC7-4EE2-BD88-BE3FBE0E2097@xxxxxxxxxxxxxxxx
>> Looks like a problem with the drivers.
>> AFAIK, ndistest for wi-fi adapters does not check scenario of association
>> by
>> BSSID
>> (or the latest version does this?) so it is quite possible that the
>> vendor
>> forgot to test this.
>>
>> Regards,
>> --PA
>>
>> "Benoît Bousquet" wrote:
>>> My NDIS IM driver is offering Wi-Fi services to a user-mode application,
>>> through IOCTL calls (the driver generates NdisRequest calls to its bound
>>> adapter). Currently, a typical association proceeds as follows (and it
>>> works
>>> quite well):
>>>
>>> OID_802_11_INFRASTRUCTURE_MODE
>>> OID_802_11_AUTHENTICATION_MODE
>>> OID_802_11_ADD_WEP (if needed)
>>> OID_802_11_WEP_STATUS
>>> OID_802_11_BSSID
>>> OID_802_11_SSID
>>>
>>> I have, however, run across an issue when faced with multiple access
>>> points
>>> using the same SSID. I was under the impression (after reading the DDK
>>> docs
>>> over and over) that an OID_802_11_SSID request would establish the
>>> association AND that it would use the currently set BSSID value to
>>> further
>>> restrict its AP selection. On both adapters I tested with (a lousy DLink
>>> DWL-122 USB gizmo and a reliable Cisco Aironet 350 PCMCIA card) the
>>> behavior
>>> seemed erratic - the DLink seemed to ignore my BSSID setting and just
>>> picked
>>> the AP with the higher RSSI, and the Cisco apparently did something
>>> similar
>>> (I couldn't do more extensive tests with it yet).
>>>
>>> Am I doing something wrong or just plain missing a step?
>>>
>>> Sample association that doesn't always behind to the desired BSSID:
>>> - OID_802_11_INFRASTRUCTURE_MODE:
>>> Ndis802_11Infrastructure
>>> - OID_802_11_AUTHENTICATION_MODE
>>> Ndis802_11AuthModeOpen
>>> - OID_802_11_WEP_STATUS
>>> Ndis802_11WEPDisabled
>>> - OID_802_11_BSSID
>>> 01:02:03:04:05:06 (desired AP's BSSID)
>>> - OID_802_11_SSID
>>> "MultipleAPName"
>>>
>>> ---
>>> Benoît Bousquet
>>>
>>>
>>>
>
>
.
- References:
- Wi-Fi AP selection by BSSID
- From: Benoît Bousquet
- Wi-Fi AP selection by BSSID
- Prev by Date: Re: NDIS IM and hidden proxy
- Next by Date: Re: Direct access to devices....
- Previous by thread: Wi-Fi AP selection by BSSID
- Next by thread: basic question about porting 32 bit driver to 64 bit windows
- Index(es):
Relevant Pages
|