John H. Robinson, IV wrote:
James G. Sack (jim) wrote:
So, boy-o-boy, I would be your friend forever if you could actually show
(some) recipes for the complete commandline sequence for wireless
setup/shutdown -- including dhclient and wep_supplicant (as req'd),
..pleeeease.
I have no idea about wep_supplicant as I have never used it.
[snip]
-john
Okay, now that two people have misspelled the word, I feel compelled to
correct the error: it's wpa_supplicant (WPA!).
You would not explicitly use it unless you use WPA or WPA2 on your
access point. If you use NetworkManager, then you use it without knowing
it. Eventually, all Wifi connections invoked via either the KDE or Gnome
GUI's (and probably others) will also use it to do much of the heavy
lifting.
Also, if you do decide to use WPA(2) on your AP - and why wouldn't you?
- then know that the Windows wifi driver cannot handle it without a
patch (KB917021 is the XP update, I think - look it up yerself) which is
not part of any Windows Update package. Of course, this could be good:
keeps most Windows users off your AP.
BTW, based on following various wifi-related developer mailing lists,
the consensus is that the reason wifi still sucks in Linux is because of
crappy Linux wifi chipset drivers. And that not only because of
uncooperative chipset makers, but also because of stubborn "Don't tell
me how to write my code" project maintainers.
Wifi Land is still in Windows World. Funny thing is though, when it
works in Linux, it generally works better than in Windows, despite the
lack of available info from the mfrs.
--
Best Regards,
~DJA.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
