Quoting Dan Williams <[EMAIL PROTECTED]>:
> All the wireless keys, preferred network, and which networks you're
> actually allowed to connect to are stored per-user, as designed, and
> also as designed, NetworkManager won't attempt to connect to a wireless
> network without that data since it couldn't possibly know which one to
> connect to.
no offense intended, but I still disagree with that design choice. It means you
cannot use NM in a situation where you have wireless network and network-based
login (e.g. Kerberos/Hesiod, NIS, etc). In the current design you have to
already be logged in in order to start the wireless network, which means you
have to have a local account.
IMNSHO it would be much better to store this information globally so that NM can
choose from pre-defined networks before the user is logged in. This certainly
works fine for WEP or unprotected networks, and even for shared-key WPA
networks. It might not work as well for interactive 802.1x authentication...
Even Windows will setup the network before the login process, assuming the
wireless network was configured a priori! How could Windows get something
right and Linux not?
> Dan
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
