WPA broken for NetworkManager, fine with wpa_supplicant

giddie · 2009-07-02 11:27:09

I've been going around in circles for days with this issue. I've had no problem with WiFi since I installed Arch in March, then a few days ago it stopped working. I can't figure out what update it was that broke it. I've tried reverting the kernel, networkmanager, and network plasmoid with no change.

Hardware:
Macbook Pro 3,1
0b:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)

I have no problem connecting by manually configuring wpa_supplicant, but NetworkManager reports the following:

NetworkManager: <info>  Activation (wlan0) starting connection 'New Wireless Connection'                               
NetworkManager: <info>  (wlan0): device state change: 3 -> 4                                                           
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...                                  
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...                                    
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...                                
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.                                     
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...                                 
NetworkManager: <info>  (wlan0): device state change: 4 -> 5                                                           
NetworkManager: <info>  Activation (wlan0/wireless): access point 'New Wireless Connection' has security, but secrets are required.                                                                                                           
NetworkManager: <info>  (wlan0): device state change: 5 -> 6                                                           
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.                                   
NetworkManager: <WARN>  update_one_setting(): Failed to update connection secrets: 1 802-1x                            
NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.                
NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.     
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...                                  
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...                                    
NetworkManager: <info>  (wlan0): device state change: 6 -> 4                                                           
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...                                
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.                                     
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...                                 
NetworkManager: <info>  (wlan0): device state change: 4 -> 5                                                           
NetworkManager: <info>  Activation (wlan0/wireless): connection 'New Wireless Connection' has security, and secrets exist.  No new secrets needed.                                                                                            
NetworkManager: <info>  Config: added 'ssid' value 'Ether'                                                             
NetworkManager: <info>  Config: added 'scan_ssid' value '1'                                                            
NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'                                                       
NetworkManager: <info>  Config: added 'auth_alg' value 'OPEN'                                                          
NetworkManager: <info>  Config: added 'psk' value '<omitted>'                                                          
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.                                   
NetworkManager: <info>  Config: set interface ap_scan to 1                                                             
NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> disconnected
NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associated
NetworkManager: <info>  wlan0: link timed out.
NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> disconnected
NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associated
NetworkManager: <info>  Activation (wlan0/wireless): association took too long.
NetworkManager: <info>  (wlan0): device state change: 5 -> 6
NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets
NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> disconnected
NetworkManager: <WARN>  get_secrets_cb(): Couldn't get connection secrets: User refused to supply secrets.
NetworkManager: <info>  (wlan0): device state change: 6 -> 9
NetworkManager: <info>  Activation (wlan0) failed for access point (Ether)
NetworkManager: <info>  Marking connection 'New Wireless Connection' invalid.
NetworkManager: <info>  Activation (wlan0) failed.
NetworkManager: <info>  (wlan0): device state change: 9 -> 3
NetworkManager: <info>  (wlan0): deactivating device (reason: 0).
NetworkManager: <info>  Policy set 'Auto eth0' (eth0) as default for routing and DNS.

djszapi · 2009-07-08 21:34:15

With other distribution/livecd can it work ? Why don't you take backup generally from your system ?

giddie · 2009-07-09 09:25:58

Well, I have daily backups of my system made automatically, but that doesn't help too much -- I don't know exactly what caused the change. I upgraded the kernel shortly before, but I'd rebooted and everything had worked fine. The problems also happened shortly after the large mkinitcpio upgrades, but I don't see how that could be responsible, given that everything was fine after I upgraded the kernel.

I might have a go with a graphical live cd of some kind. In the meantime wpa_supplicant is working, so I can live. It's just a real pain.

djszapi · 2009-07-11 15:54:11

It's not a big pain, because you can take the desired command to /etc/rc.local to connect automatically at pc startup.

if you guess mkinitcpio update cause the problem, you can which file was intalled by this, with pacman -Ql mkinitcpio.

giddie · 2009-07-11 16:04:06

Thank you for answering. I was really hoping someone might have an idea what could have gone wrong with networkmanager, or maybe find someone else who was experiencing the problem. I'm aware of ways to work around it, but I would really rather have networkmanager working correctly.

zyghom · 2009-07-20 17:36:15

I have same problem for last few days - don't really know where the problem is

giddie · 2009-07-21 08:05:12

@zyghom => I'd be interested to know what card you have (from lspci), and what driver you're using. Also, are you able to pinpoint the day in stopped working? What do the Pacman logs say was updated on that day? I can only assume it was some package update that broke it for me, but I can't figure out what!

Oh, and have you checked that it works OK for unsecured networks? I'm still able to connect using wpa_supplicant, and networkmanager still works for unsecured networks.

Last edited by giddie (2009-07-21 08:05:36)

giddie · 2009-07-21 09:40:59

I decided to give Wicd a try today. It connects perfectly for me. I can see an option for Wicd in KDE's Hardware settings, but the "Apply" button remains greyed out, so for now I'll have to stick to Wicd's GTK interface (which I'm quite impressed with, actually). It's a pity Wicd relies on Python -- I prefer native code for system software (to reduce resource usage).

eazy · 2009-08-10 18:00:29

I have the same issue as giddie:

Intel Wifi Link 5100 (iwlagn)
03:00.0 Network controller: (8086:4232) Intel Corporation Wireless WiFi Link 5100

iwlwifi-5000-ucode 8.24.2.12-1
networkmanager 0.7.1-1
networkmanager-plasmoid-svn 1008220-1 installed as the frontend on KDE4

Connection works perfectly with netcfg.
giddie, did you open a bug report for this?

Last edited by eazy (2009-08-10 18:01:37)

giddie · 2009-08-11 11:18:59

I didn't open a bug report, no. I'm actually much happier with Wicd now than I was with NetworkManager. I just wish KDE had better integration with it already.

jelly · 2009-08-11 11:55:09

well this sounds like networkmanager calling wpa_supplicant wrong because you guys can connect with an other networkmanager applet. So the kernel updates aren't the problem or driver ones. Check on the bug tracker if the networkmanager has any bugs/reports

eazy · 2009-08-11 17:38:36

It's my fault, I mistakingly disabled KWallet and NetworkManager couldn't remember the password.

Keveam · 2009-08-11 19:20:05

eazy wrote:

I have the same issue as giddie:
Intel Wifi Link 5100 (iwlagn)
03:00.0 Network controller: (8086:4232) Intel Corporation Wireless WiFi Link 5100
iwlwifi-5000-ucode 8.24.2.12-1
networkmanager 0.7.1-1
networkmanager-plasmoid-svn 1008220-1 installed as the frontend on KDE4
Connection works perfectly with netcfg.
giddie, did you open a bug report for this?

I've having the exact same problem, with the exact same software and hardware.

sk-ethum · 2009-09-23 15:08:00

Hi there,

I've got the same issue, I think it's a network-manager bug.I found the same bug in the Ubuntu karmic beta release :

https://bugs.launchpad.net/ubuntu/+sour … bug/430551

Arch Linux

#1 2009-07-02 11:27:09

WPA broken for NetworkManager, fine with wpa_supplicant

#2 2009-07-08 21:34:15

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#3 2009-07-09 09:25:58

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#4 2009-07-11 15:54:11

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#5 2009-07-11 16:04:06

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#6 2009-07-20 17:36:15

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#7 2009-07-21 08:05:12

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#8 2009-07-21 09:40:59

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#9 2009-08-10 18:00:29

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#10 2009-08-11 11:18:59

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#11 2009-08-11 11:55:09

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#12 2009-08-11 17:38:36

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#13 2009-08-11 19:20:05

Re: WPA broken for NetworkManager, fine with wpa_supplicant

#14 2009-09-23 15:08:00

Re: WPA broken for NetworkManager, fine with wpa_supplicant

Board footer