Re: networkmanager fails to associate (ipw3945)



I'm having the same problem on FC6 with ipw2200 and WPA-PSK. Compiling
STABLE fixes it. 

>From my logs, current FC6 rpm:

Feb  7 21:57:43 localhost NetworkManager: <information> Activation (eth1/wireless): access point 'Aethernet' is encrypted, and a key exists.  No new key needed. 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: sending command 'INTERFACE_ADD eth1                wext    /var/run/wpa_supplicant ' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: response was 'OK' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: sending command 'AP_SCAN 1' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: response was 'OK' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: sending command 'ADD_NETWORK' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: response was '0' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 ssid 4165746865726e6574' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: response was 'OK' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 proto WPA' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: response was 'OK' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: response was 'OK' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 psk <key>' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: response was 'OK' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0' 
Feb  7 21:57:44 localhost NetworkManager: <information> SUP: response was 'OK' 
Feb  7 21:57:44 localhost NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) complete. 
Feb  7 21:57:52 localhost NetworkManager: <information> Activation (eth1/wireless): disconnected during association, asking for new key. 
Feb  7 21:57:52 localhost NetworkManager: <information> Activation (eth1) New wireless user key requested for network 'Aethernet'. 

NetworkManager STABLE:

[...]
Feb  7 22:02:26 localhost NetworkManager: <info>  SUP: response was 'OK' 
Feb  7 22:02:26 localhost NetworkManager: <info>  SUP: sending command 'ENABLE_NETWORK 0' 
Feb  7 22:02:26 localhost NetworkManager: <info>  SUP: response was 'OK' 
Feb  7 22:02:26 localhost NetworkManager: <info>  Activation (eth1) Stage 2 of 5 (Device Configure) complete. 
Feb  7 22:02:26 localhost NetworkManager: <info>  Old device 'eth1' activating, won't change. 
Feb  7 22:02:27 localhost NetworkManager: <info>  Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to access point 'Aethernet'. 
Feb  7 22:02:27 localhost NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled. 
Feb  7 22:02:27 localhost NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) started... 
[...]

then gets IP & works!

Volker




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]