Search Linux Wireless

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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).

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux