Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
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.
Hello all. I've been struggling the past few days to resolve an issue I'm having. I have followed all the steps in ndiswrapper wiki and had no problems with my box recognizing the wireless adapter. I use network manager to connect to my router. I can connect perfect when my router is set to 'Open' (no security) and I'm able to gain an IP address. However, once I set WPA on the router and try connecting the same exact way through networkmanager, I see that it can't retrieve an IP now. The passphrase I type into networkmanager when it prompts me is correct.
I have wpa_supplicant installed but I have no idea if I have it configured correctly or if I even need to worry about that. I've hit a brick wall. ANy suggestions?
Here is some of the output code I get:
Code:
Nov 17 05:17:33 localhost NetworkManager: <info> User request for activation of wlan0.
Nov 17 05:17:33 localhost NetworkManager: <info> Activating device wlan0
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0/wireless): access point 'Auto TheHouse' has security, but secrets are required.
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 17 05:17:33 localhost NetworkManager: Missing required value 'key-mgmt'.
Nov 17 05:17:33 localhost NetworkManager: Missing or invalid key management
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto TheHouse' has security, and secrets exist. No new secrets needed.
Nov 17 05:17:33 localhost NetworkManager: <info> Config: added 'ssid' value 'TheHouse'
Nov 17 05:17:33 localhost NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Nov 17 05:17:33 localhost NetworkManager: <info> Config: added 'psk' value '<omitted>'
Nov 17 05:17:33 localhost NetworkManager: <info> Config: added 'proto' value 'WPA RSN'
Nov 17 05:17:33 localhost NetworkManager: <info> Config: added 'pairwise' value 'TKIP CCMP'
Nov 17 05:17:33 localhost NetworkManager: <info> Config: added 'group' value 'WEP40 WEP104 TKIP CCMP'
Nov 17 05:17:33 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 17 05:17:33 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
Nov 17 05:17:36 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 3
Nov 17 05:17:37 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 3 -> 4
Nov 17 05:17:37 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 4 -> 5
Nov 17 05:17:37 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 5 -> 6
Nov 17 05:17:40 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 6 -> 0
Nov 17 05:17:40 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
Nov 17 05:17:43 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 3
Nov 17 05:17:45 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 3 -> 4
Nov 17 05:17:45 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 4 -> 5
Nov 17 05:17:45 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 5 -> 6
Nov 17 05:17:48 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 6 -> 0
Nov 17 05:17:48 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
Nov 17 05:17:51 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 3
Nov 17 05:17:52 localhost NetworkManager: <info> Activation (wlan0/wireless): disconnected during association, asking for new key.
Nov 17 05:17:52 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 3 -> 0
Nov 17 05:17:53 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 4
Nov 17 05:17:53 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 4 -> 0
Nov 17 05:17:58 localhost NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: applet.c.2997 (get_secrets_dialog_response_cb): canceled.
Nov 17 05:17:58 localhost NetworkManager: <info> Activation (wlan0) failed for access point (TheHouse)
Nov 17 05:17:58 localhost NetworkManager: <info> Marking connection 'Auto TheHouse' invalid.
What is in /etc/wpa-supplicant/wpa_supplicant.conf file
Brian
Welp, I got my networkmanager working now with WPA. It is now connected to my router. But here is my wpa_supplicant.conf. Now iirc, it wont work without the
Code:
#psk="mypassphrase"
. Once I added that in, it worked. Dunno if it was just a coincidence.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
I myself don't like NetworkManager. I would do it like this. I don't know how to make NetworkManager to use it. But I have a thought and add this line to the following to the end of /etc/sysconfig/network-scripts/ifup-wireless.
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
If it does not help the only other way I know is manually adding the following to certain files and disable NetworkManager.
Disable NetworkManager, run these two commands as root.
/sbin/service NetworkManager stop
/sbin/chkconfig --level 345 NetworkManager off
Load the ndiswrapper module in /etc/modprobe.conf. Add this line to it.
alias wlan0 ndiswrapper
Next you should have /etc/sysconfig/network-scripts/ifcfg-wlan0 configured for nic. I assume setup as DHCP and ONBOOT=YES. If unsure what should be ther post the contents.
If there is a ifcfg-eth0 then make sure it has ONBOOT=NO
Now add this line to the end if /etc/sysconfig/network-scripts/ifup-wireless
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
Well, I got to test a few things out. The first step did not work for me because this linux box doesn't recognize that I have a wlan0 until I actually go into the terminal and initialize it by doing a:
Code:
iwconfig wlan0
Is there any way for me to have that speck of code run after a reboot or startup?
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
I jump the gun here. You did not mention the nic that is invloved and the chipset it is using. Plus the module it uses. I define the wpa_supplicant with the use of Ndiswrapper module. If you have no wlan0 then you may not be using ndiswrapper. This info we need to know to help select the correct -D option for this interface.
I jump the gun here. You did not mention the nic that is invloved and the chipset it is using. Plus the module it uses. I define the wpa_supplicant with the use of Ndiswrapper module. If you have no wlan0 then you may not be using ndiswrapper. This info we need to know to help select the correct -D option for this interface.
Brian
Well, I think I'm making some progress. I'm convinced now that networkmanager isn't very good on FC8, so I'm going your route. I've uninstalled NM and am now currently connected to my router using only ndiswrapper (Buffalo Wireless-N USB adapter), wpa_supplicant, dhclient.
My current process to get there is as follows:
ifconfig wlan0 up
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
dhclient wlan0
This weekend I'll most likely have time to mess with the code below the equal sign horizontal rule. I'll keep you posted.
For some reason, I have almost the same problem. Only the difference is mine originally worked. After 1 batch of updates that I installed, next time I reboot the laptop, the wireelss is just not working anymore.
I usually used NetworkManager and it used to work like a charm, but as I said above, it just stops working.
Before I started using NetworkManager, I have been just using the system-config-network and configured the passphrase from there (since mine's just Hex) and I can connect through. But this time I get "failed. Please check cable?" or something similar.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.