Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a problem connecting to WPA-PSK-protected networks. Short description: I have Thinkpad T43p, WLAN-card is recognized and running. Several years ago, when NetApplet was too young and unusable, I decided to write a script, which switched on and off my WLAN (including connection to the router using wpa_supplicant). A month ago I gave a try to NetApplet. It looks quite good now, and I wanted to use it regularly. Unfortunatelly, I could not connect to my router.
On the week-end I switched from Debian to Ubuntu - I installed Ubuntu 11.10. Under "Unity" I could connect to my router, under GNOME - not. Since I'm going to use GNOME, I would like to get my NetApplet and WLAN running.
Here is my question: can anyone give me a hint, what I should to do to resolve the issue? I think, it has anything to do with my wpa_supplicant configuration, which I created when I used my old scripts, but I'm not quite sure.
Additional information: when I try to connect to WLAN using NetApplet, it tries several seconds and then asks for a password, although I have it already set in the network profile.
Distribution: Fedora 18, Slackware64 13.37, Windows 7/8
Posts: 386
Rep:
I actually just did this in Puppy Linux. Puppy is designed to be run as a Live distro that's not designed to be run like a standard everyday distro so it requires you to manually (re)-enter the network info every time you start the machine!
To resolve this I had to create a login script to connect to the WPA2 router. Basically all you need to do is edit the wpa_supplicant's config file and then reference that file when calling the wpa_supplicant program.
Personally, I don't bother with a NM anymore. I have wpa_supplicant configured to start at boot, and leave it to it. No more dropped wifi, no more bad connections etc.
However, if you must have a NM, take a look at wicd. It's about the best out there.
thanks for your hints and replies. Actually, I used to work with "Access Connections" from IBM/Lenovo. I want to be able to switch manually from cable to WLAN. That's why I want to get NetworkManager running.
Quote:
Originally Posted by Roken
Personally, I don't bother with a NM anymore. I have wpa_supplicant configured to start at boot, and leave it to it. No more dropped wifi, no more bad connections etc.
However, if you must have a NM, take a look at wicd. It's about the best out there.
To be honest, I do not really understand the realtionship between NetworkManager and wpa_supplicant. Someone says "they must run together", someone says "NetworkManager has its own WPA-driver, and that's why they conflict". Does anyone know the real situation?
I can't be certain, but when I have used a Network Manager, a quick look at ps -A (or your task manager if you use one) will confirm that wpa_supplicant is still running. As such, I suspect that NMs are just basically another layer over the top of wpa_supplicant. My own experience, however, is that NMs can cause problems. Whenever I've used one (whether it be gnome-network-manager, wicd etc) I've had problems with stalling connections, dropped connections etc. Since I went directly to wpa_supplicant with no intermediate layer my wireless is rock solid.
Granted, you don't get all the pretty GUI configuration that a NM provides, and you have to take care of monitoring your network yourself if you want to know what's going on (a fairly trivial task with something like conky), but the stability IMO more than makes up for it.
NB. This may just be something peculiar to my PC, network, router etc., so YMMV.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.