Re: ath5k: problems during the connection to a sitecom AP

[Holger Schurig <hs4233@mail.mn-solutions.de>]

> When I do a scan after having loaded the driver, the iwlist
> can't report the SSID because it's hidden. I don't know if
> this is a problem but I have noticed that the reported SSIDs
> of the two APs are a little bit different. With the 3com AP
> (the working one) I get ESSID:" " (1 char blank string) while
> with the Sitecom AP ESSID:"" (0 chars empty string).

Okay, that could very well be the problem.


Side node: it doesn't buy you anything to "hide" the SSID of an 
AP. Actually, you can't really hide. The hidden bit only makes 
the AP lie about the SSID in it's beacons, but for other 802.11 
WLAN protocol messages (like Association Request, Assoc Resp) 
the SSID has to be send in cleartext anyway.

So turn of this stupid thingy. This also makes your roaming 
slightly faster and use slightly less battery (because the 
client doesn't need to probe the AP if it has the right, 
expected, SSID. The client knows in an instant that this is the 
case).