Network Manager won't remember WAP settings in Ubuntu
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Network Manager won't remember WAP settings in Ubuntu
Well, to give some background, I set my computer-illiterate mother up with a Dell E1405 running Ubuntu, and after hours upon hours of trying to integrate information from several different forums (using ndiswrapper, dell's proprietary drivers, and wpa_supplicant), I was finally able to connect it to our WAP. Said WAP uses WPA encryption and does not broadcast its SSID.
Unfortunately, Network Manager will not retain the WAP settings after a reboot. I'm still something of a newbie as far as Linux is concerned, and am not quite sure how to set up a script to automatically connect, as I can't seem to connect through iwconfig.
I'm not sure what other information would be relevant, but if there's anything that could help someone to help me figure this out, let me know and I'll get it ASAP. Thanks!
I never had much luck with the GUI tools. And I do not need to use ndiswrapper as my wireless chip is suported by the kernel.
But I can make my wireless network connect at boot, with this in my /etc/network/interfaces file:
# This defines the usual loopback interface
iface lo inet loopback
# eth1 is my wireless interface, and I want it brought up at boot
# I like a static IP, replace "static" with "dhcp"
# if you want to be allocated a dynamic IP by your router
iface eth1 inet static
# This is the broadcast address for my network, yours may be different
# This is the static IP I want on my LAN
# miss the next line out if you are using DHCP
# This is the netmask for my network, yours may be different
# This is the IP of my router, yours may be different
# This is my WPA Passphrase, yours will be different
# This is the SSID of my wireless AP, you'll need this
# even if your AP isn't broadcasting its name
# This is the channel my AP is working on
I boot, it connects. Easy. Hope this solves your problem.
Tredegar - I know that that should work, but for some reason it doesn't. I'd tried entering the configuration into /etc/network/interfaces before, but it didn't work then. I tried it again using your guide, but that didn't work, either.
It seems that if there is any entry at all for my wireless adapter (also eth1) in /etc/network/interfaces, the NetworkManager applet won't even see it. As for trying to work without NetworkManager, I can connect without any encryption (even WEP won't work), and this only works if I have the WAP broadcasting its SSID - not really the way I want to go.
I can connect without any encryption (even WEP won't work)
....Then there is something going wrong with your encryption / authentication.
Make sure you have wpa_supplicant installed. Other packages I have installed and you may need are:
libiw28 kwlan (but I can't make this work) wpagui (but I can't make this work either!) wireless-tools wlassistant (most of the time, this is not a helpful piece of software!)
Give your AP/Router a name (SSID) and make sure it is set to use WPA-PSK (Pre-Shared-Key) encryption and enter a passphrase for WPA-PSK into your Ap/Router. My passphrase has no spaces.
Make sure it is broadcasting its name (this is harmless). Make sure you know the channel it is using.
Edit your /etc/network/interfaces as in my post #2 above. sudo ifdown eth1
sudo ifup eth1
You should be connected. If you are still having trouble, please post the contents of /etc/network/interfaces, the output of ifconfig and the IP address of your router/AP
I do not understand why you are having trouble - I have set up two different laptops like this, both with kubuntu 6.06.1, and they worked straight away.
"I was finally able to connect it to our WAP. Said WAP uses WPA encryption and does not broadcast its SSID.
Unfortunately, Network Manager will not retain the WAP settings after a reboot."
Tredegar, if I understand this correctly, he is able to connect WPA, so that means that all the software is installed and loaded.
The way I understand this is that he configures the network manager, it connects and works, but when he reboots the configuration is wrong.
If you're a KDE user, then I can't help you. Under Gnome, click Desktop->Preferences->Sessions->Save the current session. There should be a radio button for you to always save the session, as well. A lot of people first encounter session management when their sound disappears everytime they reboot.
Quake - exactly. I do have everything installed, but can only connect using WPA through network manager's UI. If I want to connect through the command line or automatically through /etc/network/interfaces, I have to turn off all encryption and have it broadcast its SSID. I've tried every conceivable combination already, and do not want to toy around with my WAP's settings anymore, now that I can at least connect to it using the settings I want.
That I prevent my WAP from broadcasting its SSID should be irrelevant anyway (at least, in my own little world). I know what it is, I know what channel it's broadcasting on, I know the WPA key, and I know how to get the passkey itself through the command line, and have tried that, too. I also know firsthand how easy it is for a script-kiddie to break WEP or WPA if the SSID is known, so I'd prefer to stay away from that if possible. I'm a Linux newbie, relatively speaking, but I've been working with computers since I was about five, so I've worked with networking, both wired and wireless, many times before.
As for saving sessions, I am using Gnome. I remember trying something similar, through the System menu, but I'll give this a shot and post back. Thanks!
You are right about installed software - dmravaet seems to have the required resources.
But dmravaet wants to connect wirelessly at boot, and this means a CLI / script fix, not a GUI fix. "Saving sessions", just keeps windows open in my experience, and yes, I too have answered many threads about "Why do I get all these things starting up when I login, why won't they go away?". I wish the clever guys would set the default to "Start with an empty session". Give it time... . . . . !
I have been doing some testing.....
If I set my AP not to broadcast its SSID, then the /etc/network/interfaces setup I gave you does not work, and will not connect, even if I comment out the line wpa-ssid Whatitscalled
[I didn't try setting it to wpa-ssid Hidden, but it's late at night for me.]
I don't mind my AP broadcasting its name, because my security is set with WPA, which seems to be quite robust (compared to weak WEP, please correct me if I am mistaken here). It also seems to me that my laptop, when it is trying to bring the wireless connection up, needs to know which AP to associate with. How can it do this if the available APs are not named? It would have to try all of them, attempt WPA negociation, try again etc. It seems more sensible to name it, and then let WPA sort out the security.
My additional level of "security", is that I have set my wireless AP so that it will only begin to consider allowing connections from certain MAC addresses (like the MAC of my wireless laptop). I don't think there are many people within wireless range who know both how to spoof a MAC address (they're probably running windows) and crack WAP.
Besides, most of my neighbours are running completely open networks - easier fishing there.
So, please, try enabling "Broadcast SSID" in your router / AP, and try my interfaces setup again. I hope you'll find that it works.
I've never tried using a hidden ESSID. I didn't like the network manager GUI. To be blunt, it's a nice thing for a traveling laptop, but it's a real POS for a desktop if there are multiple APs in the area. I did try it once, and it kept trying to disconnect me and reconnect me to random APs through the day. I uninstalled it and made it and its problems go away. My script to get WPA working consisted simply of creating a wpa_supplicant.conf from the output of wpa_passphrase, and then running wpa_supplicant from the interfaces file as follows:
1. an aptitude for making desirable discoveries by accident.
2. good fortune; luck
3. trying vainly and repeatedly to find a script/CLI fix, and unwittingly fixing it through the GUI in the process.
Apparently, it will automatically connect provided the SSID is broadcast, and suddenly it's playing nice with the MAC filter as well.
"I don't mind my AP broadcasting its name, because my security is set with WPA, which seems to be quite robust (compared to weak WEP, please correct me if I am mistaken here)."
The reason I'd rather my SSID not be broadcast is it just makes it that much easier to break, not that it isn't relatively easy as it is - WPA-PSK, while much more secure than WEP, can be cracked relatively easily (http://docs.lucidinteractive.ca/inde...less_Networks). WPA-RADIUS and WPA2 seem to be much more effective, so I'll probably look into that, but in the meantime, we'll just have to operate under the assumption that anything transmitted or received could be intercepted (probably a good rule of thumb regardless).
Anyways, tredegar, quake: THANKS. You may not have solved the problem perfectly, but you've been a tremendous help nonetheless.
I'm connecting through the GUI - works automatically as long as SSID is broadcasting. Couldn't get it working through CLI/script. If I even make a mention of eth1 in /etc/network/interfaces, I can't connect, but since I've fixed it through the GUI, that's good enough for now.
As for the link being dead, it's not, it just took on the end parenthesis by mistake, so here it is again, as it should appear.