PDA

View Full Version : Wlan problem no clues yet


mdyehiya
2008-07-07, 10:19 PM CDT
I'm unable to connect to the wifi after last week. There were no changes in the hardware setting;
I suspect may be due to update I receive constantly.

Can anyone help me fixing this issue.

/var/log/wpa_supplicant.log


Trying to associate with 00:1d:7e:1f:c9:6d (SSID='linksys' freq=2437 MHz)
Associated with 00:1d:7e:1f:c9:6d
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Associated with 00:1d:7e:1f:c9:6d
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
WPA: EAPOL-Key Replay Counter did not increase - dropping packet
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Authentication with 00:00:00:00:00:00 timed out.


/var/log/messages

Jul 8 00:15:44 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 8 00:15:44 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 8 00:15:44 localhost NetworkManager: <info> Activation (wlan0/wireless): access point 'linksys' has security, but secrets are required.
Jul 8 00:15:44 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 8 00:15:44 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
Jul 8 00:15:52 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 8 00:15:52 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 8 00:15:52 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 8 00:15:52 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 8 00:15:52 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 8 00:15:52 localhost NetworkManager: <info> Activation (wlan0/wireless): connection 'linksys' has security, and secrets exist. No new secrets needed.
Jul 8 00:15:52 localhost NetworkManager: <info> Config: added 'ssid' value 'linksys'
Jul 8 00:15:52 localhost NetworkManager: <info> Config: added 'scan_ssid' value '1'
Jul 8 00:15:52 localhost NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jul 8 00:15:52 localhost NetworkManager: <info> Config: added 'psk' value '<omitted>'
Jul 8 00:15:52 localhost NetworkManager: <info> Config: added 'proto' value 'WPA RSN'
Jul 8 00:15:52 localhost NetworkManager: <info> Config: added 'pairwise' value 'TKIP CCMP'
Jul 8 00:15:52 localhost NetworkManager: <info> Config: added 'group' value 'WEP40 WEP104 TKIP CCMP'
Jul 8 00:15:52 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 8 00:15:52 localhost NetworkManager: <info> Config: set interface ap_scan to 1
Jul 8 00:15:52 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 0
Jul 8 00:15:52 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
Jul 8 00:15:53 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 3
Jul 8 00:15:54 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul 8 00:15:54 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 3 -> 4
Jul 8 00:15:54 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 4 -> 5
Jul 8 00:15:54 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 5 -> 6
Jul 7 23:15:55 localhost avahi-daemon[2256]: Registering new address record for fe80::21e:8cff:fe2e:eb60 on wlan0.*.
Jul 8 00:15:57 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 6 -> 0
Jul 8 00:15:57 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
Jul 8 00:15:58 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 4
Jul 8 00:15:59 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 4 -> 5
Jul 8 00:15:59 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 5 -> 6
Jul 8 00:16:02 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 6 -> 0
Jul 8 00:16:02 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
Jul 8 00:16:03 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 4
Jul 8 00:16:04 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 4 -> 5
Jul 8 00:16:04 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 5 -> 6
Jul 8 00:16:07 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 6 -> 0
Jul 8 00:16:07 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
Jul 8 00:16:08 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 4
Jul 8 00:16:09 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 4 -> 5
Jul 8 00:16:09 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 5 -> 6
Jul 8 00:16:12 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 6 -> 0
Jul 8 00:16:12 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
Jul 8 00:16:13 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 4
Jul 8 00:16:14 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 4 -> 5
Jul 8 00:16:14 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 5 -> 6
Jul 8 00:16:17 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 6 -> 0
Jul 8 00:16:17 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 2
Jul 8 00:16:17 localhost NetworkManager: <info> Activation (wlan0/wireless): association took too long.
Jul 8 00:16:17 localhost NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets
Jul 8 00:16:17 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 2 -> 0
Jul 8 00:16:18 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 4
Jul 8 00:16:18 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 4 -> 0
Jul 8 00:16:22 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 0 -> 4
Jul 8 00:16:22 localhost NetworkManager: <info> (wlan0) Supplicant interface state change: 4 -> 0
Jul 8 00:16:32 localhost NetworkManager: <info> wlan0: link timed out.
Jul 8 00:16:32 localhost NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: applet-device-wireless.c.1240 (get_secrets_dialog_response_cb): canceled.
Jul 8 00:16:32 localhost NetworkManager: <info> Activation (wlan0) failed for access point (linksys)
Jul 8 00:16:32 localhost NetworkManager: <info> Marking connection 'linksys' invalid.
Jul 8 00:16:32 localhost NetworkManager: <info> Activation (wlan0) failed.
Jul 8 00:16:32 localhost NetworkManager: <info> Deactivating device wlan0.
Jul 7 23:16:32 localhost avahi-daemon[2256]: Withdrawing address record for fe80::21e:8cff:fe2e:eb60 on wlan0.

bbfuller
2008-07-08, 01:52 AM CDT
Hello mdyehiya

Try booting with the previous kernel from the grub boot menu.

Quite a lot of people are having trouble with the latest kernel and if the old one works then it's sensible to wait for a replacement.

If that works for you, there is a way to make that previous kernel the default for the time being to save having to select it each time.

There is also a way to preserve more than two kernels on your system. after all, if you follow the strategy above and and a further updated kernel is broken you will have lost your working kernel in the upgrade.

Post back if you want any pointers on any of that.

gmiller1018
2008-07-08, 02:22 PM CDT
I am having the same problem with my wlan and the b43 driver. This started when I upgraded to 2.6.25.9-76.fc9.i686 from 2.6.25.6-55.fc9.i686 . Dropping back to 2.6.25.9-76.fc9.i686 fixed the problem. My wap_supplicant log file was basicly the same as mdyehiya was.

Thanks for the suggestion bbfuller.

mdyehiya
2008-07-08, 05:49 PM CDT
Thanks guys, that really solved my purpose...
Now I'm able to connect with my previous version of kernel

Alex-Grim
2008-10-03, 11:47 PM CDT
You do not have to rollback your kernel. If you compiled ndiswrapper, and did NOT yum it, then you must REcompile it every time you update your kernel. You do not have to reinstall the drivers, and reedit the config files, you only have to recompile ndiswrapper itself and reinstall it.

This may help you with your wireless, in the future, as it does for many people: http://linuxintro.com/?action=ViewEn...e=900072752405
Please do not mind the appearance at the moment, i am in the middle of remodeling right now. Also, the "Prev" and "Next" links have to be fixed, so to find the next article in the series, from the main menu, go to Distros - > Fedora and then click the next one.

Hope this helps you too