Re: Can't use SSID for authentication (bug?)

Hi Vitor,

On Sat, 13 Mar 2004, Vitor Duarte wrote:

>
> I have a Lynksys USB (ver 2.6) and I was never able to use this driver,
> whatever I try. Finally I can use it... if the access point don't use
> the SSID for authentication!
>
> If the access point just accepts clients with the correct ssid
> I get from this driver in debug mode:
>
> eth1 param: ssid SpeedTouch892028 (5370656564546F756368383932303238) mode infra ch 10 wep disabled key 0 keylen 0
> ...
> eth1 BSS table (curr=00000000, new=00000000):
> 0xcd583ba0: bssid 00:02:2d:89:20:28 channel 6 ssid   (20) capa x0001 rates 82 84 0B 16 rssi 5 link 0 noise 0
> eth1 BSS table (curr=00000000, new=00000000):
> 0xcd583ba0: bssid 00:02:2d:89:20:28 channel 6 ssid  peedTouch892028 (20) capa x0001 rates 82 84 0B 16 rssi 6 link 0 noise 0
> eth1: state 1 -> 6 (JOINING)
> eth1 bss table entry cd583ba0: essid didn't match
>
> (note the changing SSID)
> ...
> [at76c503a from cvs tarball]
>
> Can this be a bug or is just not supported?

How a SSID is cloaked depends on the manufacturer, up to now the driver
treats only SSIDs of length 0 or SSIDs containing zero bytes as cloaked.
Your access point seems to use ' ' as a cloaked SSID.

What's the brand of your AP?

The second line is a bug in the driver: in the first round the
driver probes on all channels with the ANY SSID (to provide a complete
list of the APs in the environment), in the second round it
uses the configured SSID (to get correct answers from APs with cloaked
SSID). In your case it got a beacon with a cloaked SSID afterwards which
partly (?) overwrote the SSID field, but forgot to write the terminating
\0.

I've checked in a new version of at76c503.c (1.44) which should fix your
problem. Couldn't test it here, 'cause my AP doesn't use your kind of
cloaked SSID. Please post your test results!

/Jörg