WPA WLAN stopped working - Help!

[roachy]

Hi all,

Just recently started having problems with WPA encrypted wireless networks using FC9.....

Last night at home I was unable to connect to the WPA encrypted network at home using my laptop with an Intel 3945BG wireless adapter. I got round the issue by unencrypting the network temporarily (and it worked fine). Unfortunately I didn't have time to troubleshoot the issue properly - I assumed it to be an issue with the router/lan at home.

On coming to the office today though I'm experiencing the same issue. Unfortunately unsecuring a corporate network is not an option. Please bear in mind this has been working, and currently works for XP and Vista clients, so it's not an AP issue.

Initially I got the following in /var/log/messages

Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 11 10:38:21 prlappy NetworkManager: <info> (wlan0): device state change: 4 -> 5
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0/wireless): access point 'Auto RURALCONCEPTS' has security, but secrets are required.
Jul 11 10:38:21 prlappy NetworkManager: <info> (wlan0): device state change: 5 -> 6
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 11 10:38:21 prlappy NetworkManager: Missing or invalid key management
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 11 10:38:21 prlappy NetworkManager: <info> (wlan0): device state change: 6 -> 4
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 11 10:38:21 prlappy NetworkManager: <info> (wlan0): device state change: 4 -> 5
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto RURALCONCEPTS' has security, and secrets exist. No new secrets needed.
Jul 11 10:38:21 prlappy NetworkManager: <info> Config: added 'ssid' value 'RURALCONCEPTS'
Jul 11 10:38:21 prlappy NetworkManager: <info> Config: added 'scan_ssid' value '1'
Jul 11 10:38:21 prlappy NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jul 11 10:38:21 prlappy NetworkManager: <info> Config: added 'psk' value '<omitted>'
Jul 11 10:38:21 prlappy NetworkManager: <info> Config: added 'proto' value 'WPA RSN'
Jul 11 10:38:21 prlappy NetworkManager: <info> Config: added 'pairwise' value 'TKIP CCMP'
Jul 11 10:38:21 prlappy NetworkManager: <info> Config: added 'group' value 'WEP40 WEP104 TKIP CCMP'
Jul 11 10:38:21 prlappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 11 10:38:21 prlappy NetworkManager: <info> Config: set interface ap_scan to 1
Jul 11 10:38:21 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
Jul 11 10:38:26 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 3
Jul 11 10:38:26 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 3 -> 0
Jul 11 10:38:26 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 4
Jul 11 10:38:26 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 5
Jul 11 10:38:30 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 5 -> 0
Jul 11 10:38:30 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
Jul 11 10:38:31 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 5
Jul 11 10:38:31 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 5 -> 4
Jul 11 10:38:32 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 5
Jul 11 10:38:35 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 5 -> 0
Jul 11 10:38:35 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
Jul 11 10:38:36 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 4
Jul 11 10:38:36 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 5
Jul 11 10:38:40 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 5 -> 0
Jul 11 10:38:40 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
Jul 11 10:38:41 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 4
Jul 11 10:38:41 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 5
Jul 11 10:38:41 prlappy NetworkManager: <info> wlan0: link timed out.
Jul 11 10:38:45 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 5 -> 0
Jul 11 10:38:45 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
Jul 11 10:38:46 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 4
Jul 11 10:38:46 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 5
Jul 11 10:38:46 prlappy NetworkManager: <info> Activation (wlan0/wireless): association took too long.
Jul 11 10:38:46 prlappy NetworkManager: <info> (wlan0): device state change: 5 -> 6
Jul 11 10:38:46 prlappy NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets
Jul 11 10:38:46 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 5 -> 0
Jul 11 10:39:01 prlappy NetworkManager: <info> wlan0: link timed out.
Jul 11 10:40:36 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
Jul 11 10:40:41 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0
Jul 11 10:40:41 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 4
Jul 11 10:40:41 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 0
Jul 11 10:40:56 prlappy NetworkManager: <info> wlan0: link timed out.
Jul 11 10:42:36 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
Jul 11 10:42:41 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0
Jul 11 10:42:41 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 4
Jul 11 10:42:41 prlappy NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 0
Jul 11 10:42:56 prlappy NetworkManager: <info> wlan0: link timed out.
Jul 11 10:43:46 prlappy NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: Message did not receive a reply (timeout by message bus).
Jul 11 10:43:46 prlappy NetworkManager: <info> (wlan0): device state change: 6 -> 9
Jul 11 10:43:46 prlappy NetworkManager: <info> Activation (wlan0) failed for access point (RURALCONCEPTS)
Jul 11 10:43:46 prlappy NetworkManager: <info> Marking connection 'Auto RURALCONCEPTS' invalid.
Jul 11 10:43:46 prlappy NetworkManager: <info> Activation (wlan0) failed.
Jul 11 10:43:46 prlappy NetworkManager: <info> (wlan0): device state change: 9 -> 3
Jul 11 10:43:46 prlappy NetworkManager: <info> (wlan0): deactivating device.

After some tinkering though (forcing a static IP/DNS and gateway), I get the error:

Jul 11 12:18:36 prlappy NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 11 12:18:36 prlappy NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul 11 12:18:36 prlappy NetworkManager: <info> (wlan0): device state change: 5 -> 7
Jul 11 12:18:36 prlappy NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Jul 11 12:18:36 prlappy NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul 11 12:18:36 prlappy NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Jul 11 12:18:36 prlappy NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jul 11 12:18:36 prlappy NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Jul 11 12:18:36 prlappy NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Jul 11 12:18:37 prlappy NetworkManager: <info> (wlan0): device state change: 7 -> 8
Jul 11 12:18:37 prlappy NetworkManager: <info> Activation (wlan0) successful, device activated.
Jul 11 12:18:37 prlappy NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Jul 11 12:18:37 prlappy nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/05-netfs' exited with error status 1.

Any ideas....it's driving me nuts.....

The only thing I can think of is an update on the laptop has broken networkmanager....

[bbfuller]

Hello roachy

A lot of people are having trouble with wireless after the most recent kernel update.

I suggest that as a first resort you try booting with the previous kernel from the grub boot menu.

[roachy]

Dude.....I love you

Thanks for pointing out the glaringly obvious.....working fine now.....

Thanks for the advice.....going to go and beat myself repeatedly for not checking this!!

[aceviperking]

i have the same problem. After booting from previous kernel, problem fixed. Did anyone know how to have a certain kernel boot at default? So I dont have to choose kernel every time when boot up.

Thanks,

[bbfuller]

Hello roachy

Steady on old chap, we're all frightfully English here.

Glad it helped. Don't forget to hang onto the working kernel. When you do the next kernel update the working one will be replaced and if the new one doesn't work as well..............!

If you want to talk about ways of doing that post back.

[bbfuller]

Hello aceviperking

You'll need to open up a root text editor. Open a terminal and type:

su -

The space an minus sign are important. Without them you get root access but only to your own users area. With them you get root access to the whole machine.

gedit

Will open the root text editor.

Open the file:

/boot/grub/menu.lst

and look for the line that reads:

default=0

The sections below that headed "title" are the booting options. They are counted in sequence starting from zero.

Hence the zero in the line default is the first in the sequence.

Change the number of default according to which "title" section you wish to boot automatically.

[aceviperking]

thanks bbfuller