Wade Curry wrote:
I don't bother with WPA at all. I usually just tell my AP not to
broadcast the SSID. Doing so lets me keep things simple for
visitors, but cuts down on purely accidental connections.
Except your your packets carry your SSID anyway. Not putting up a
headline doesn't mean I still can't read the story. Any decent client
can still see your AP and its SSID.
All your efforts get you is to make it more difficult for an authorized
user to connect to your AP because your hardware is not following the
spec. Dealing with many AP's in the same building or campus, none of
which are broadcasting their SSID, is a PITA. Even worse when they all
use the same SSID's (Linksys, NETGEAR, etc.).
My wireless is now down below 802.11b speeds due to *way* too
many access points.
The problem is that:
A) there is no good solution B) even if there was, I can't locate
the AP's
Exactly. There isn't a good solution technologically. If it's
possible to contact neighbors and figure out a way to cooperate...
Maybe you could share bandwidth and get some more speed and load
balancing. Who knows? If that isn't possible or preferable, then
it would appear that the best thing to do is put up with it.
Even worse, 802.11n is going to squirt crap all over the 5GHz
band, so I can't even escape ther anymore. :(
Wade Curry
syntaxman
As far as I know, 802.11n was never, and will never be ratified as a
standard. 802.11s is to be the next "Standard".
--
Best Regards,
~DJA.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
