Can't use SSID for authentication (bug?)
Vitor Duarte <[email protected]>
| Newsgroups | gmane.linux.drivers.at76c503a.user |
|---|---|
| Message-ID | <[email protected]> |
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) If the access point accepts anyone: eth1 param: ssid SpeedTouch892028 (5370656564546F756368383932303238) mode infra ch 10 wep disabled key 0 keylen 0 ... eth1 BSS table (curr=00000000, new=00000000): 0xcd5834a0: bssid 00:02:2d:89:20:28 channel 6 ssid SpeedTouch892028 (5370656564546F756368383932303238) capa x0001 rates 82 84 0B 16 rssi 6 link 0 noise 0 eth1 BSS table (curr=00000000, new=00000000): 0xcd5834a0: bssid 00:02:2d:89:20:28 channel 6 ssid SpeedTouch892028 (5370656564546F756368383932303238) capa x0001 rates 82 84 0B 16 rssi 5 link 0 noise 0 eth1: state 1 -> 6 (JOINING) eth1 find_matching_bss: returned cd5834a0 and it works (WEP and no WEP, in 2.4* and 2.6*) [at76c503a from cvs tarball] Can this be a bug or is just not supported? regards