I leave my laptop at home 95% of the time. I would like it to connect to my wireless network without me having to login. And, just as important, I'd like it NOT to DISconnect when I log off.
I'm using Fedora, but Ubuntu instructions are welcome too.
|
I leave my laptop at home 95% of the time. I would like it to connect to my wireless network without me having to login. And, just as important, I'd like it NOT to DISconnect when I log off. I'm using Fedora, but Ubuntu instructions are welcome too. |
|||
|
|
|
I guess this question was asked a while ago, but this feature has been added to recent versions of Network Manager. See here. |
|||
|
|
The issue with this idea is that the NetworkManager service takes its commands from nm-applet (or the KDE analogue, if you're in KDE. To avoid confusing myself, I'll assume you're in GNOME). There is a command-line NetworkManager interface in the repositories called cNetworkManager (that's, oddly enough, written in Python). You could try to stick a command to connect to your network using cNetworkManager in a startup script (I'm not entirely sure where you'd have to put this script, but I know it's possible :D). I don't know whether or not this approach will connect or if it'll stay connected after you logout, but i DO know that there are at least 2 issues you'll have to reconcile. 1) You'll have this script fighting with nm-applet. If you want to do this, i'd disable nm-applet from starting automatically (which should be configurable in either preferences -> sessions or preferences -> startup programs, depending on whether or not you're using fedora 11). 2) if you ever want to change networks (and do fancy things like automatically detect them), you'll either have to do so using cNetworkManager (which is a real pain), or start up nm-applet and lose your ability to keep the connection open after you logout. Best of luck, and let us know if this works! |
|||||
|
|
I had the same issue and I ended up removing NetworkManager completely and using wpa_supplicant directly instead. It works in the opposite kind of way - you have a config file with all the networks you want to connect to automatically, and a GUI that can either override it during runtime (and connect to a different network), or to change the config file. I used this tutorial to set up my Debian, and I didn't have too many issues with it (its same as Ubuntu): http://svn.debian.org/wsvn/pkg-wpa/wpasupplicant/branches/unstable/debian/README.Debian?op=file&rev=0&sc=0 |
|||
|
|
|
May be that is not an option for you, but you could setup network via config files as in the tutorial. It is for Ubuntu, but I didn't noticed the difference. Network would be switched on during OS booting process. |
|||||
|