At some point NM looses wi-fi link and tries to re-associate, failing on assert: Feb 3 20:09:51 unicorn NetworkManager: <info> Supplicant state changed: 0 Feb 3 20:09:59 unicorn NetworkManager: <info> ath0: link timed out. Feb 3 20:09:59 unicorn NetworkManager: <info> SWITCH: found better connection 'ath0/valhalla' than current connection 'ath 0/valhalla'. same_ssid=1, have_link=0 Feb 3 20:09:59 unicorn NetworkManager: <info> Will activate connection 'ath0/valhalla'. Feb 3 20:09:59 unicorn NetworkManager: <info> Device ath0 activation scheduled... Feb 3 20:09:59 unicorn NetworkManager: <info> Deactivating device ath0. Feb 3 20:09:59 unicorn dhclient: wifi0: unknown hardware address type 801 Feb 3 20:09:59 unicorn dhclient: can't create /var/lib/dhclient/dhclient-ath0.leases: No such file or directory Feb 3 20:09:59 unicorn dhclient: wifi0: unknown hardware address type 801 Feb 3 20:09:59 unicorn dhcdbd: dhclient 11697 down (9) but si_code == 0 and releasing==0 ! Feb 3 20:10:00 unicorn NetworkManager: <info> Activation (ath0) started... Feb 3 20:10:00 unicorn NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Feb 3 20:10:00 unicorn NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started... Feb 3 20:10:00 unicorn NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Feb 3 20:10:00 unicorn NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Feb 3 20:10:00 unicorn NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting... Feb 3 20:10:00 unicorn NetworkManager: file nm-device-802-11-wireless.c: line 2317 (ap_need_key): assertion failed: (security) I have madwifi drivers from svn (due to the "seems-to-be-known" bug in stable release that prevents it from working with NM) and wpa_supplicant-0.6.1. Reproducible: Sometimes Steps to Reproduce: 1. Connect to wi-fi AP 2. Sit and wait
I can't reproduce this here - are you using trunk svn or the 0.9.4 branch? (please test with the 0.9.4 branch of the madwifi drivers please) I use the 0.9.4 branch - and I've been using the 0.9.3.3 drivers and NM for ages without issue, so I am not quite sure what you mean.... Also, I don't use the madwifi useflag with wpa_supplicant.
I *think* I'm seeing this too with rtl8180 card rather than madwifi. When I force re-association NM crashes. Used to work fine in networkmanager-0.6.5_p20070823. How do I produce the nice log like Vladimir Pouzanov to confirm whether or not this is the same issue?
Can't really reproduce this one now, everything seems to be fine but I don't remember changing anything.
I too seem to be suffering from this bug when connecting to the wireless network at work using WPA2 Enterprise/PEAP with MSCHAPv2 connecting with an IPW2200, reverting to the previous NM release fixes the problems. Feb 9 12:40:17 mrhoppy NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 fragment_size 1300' Feb 9 12:40:17 mrhoppy NetworkManager: <info> SUP: response was 'OK' Feb 9 12:40:17 mrhoppy NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Feb 9 12:40:17 mrhoppy NetworkManager: <info> SUP: response was 'OK' Feb 9 12:40:17 mrhoppy NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Feb 9 12:40:22 mrhoppy NetworkManager: <debug> [1202560822.163097] wpa_parse_wpa_ie_wpa(): wpa_parse_wpa_ie_wpa: ie count botch (pairwise), count 0 left 6 Feb 9 12:40:22 mrhoppy dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason Feb 9 12:40:22 mrhoppy NetworkManager: <debug> [1202560822.865929] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'IS Mobile Media 1' Feb 9 12:40:22 mrhoppy NetworkManager: file nm-device-802-11-wireless.c: line 967 (nm_device_802_11_wireless_get_activation_ap): assertion failed: (security) If theres any more info needed just ask and il try and help.
Have you tried with 0.7.1-r6 ?
(In reply to comment #5) > Have you tried with 0.7.1-r6 ? > Closing since current stable includes lots of fixes regarding to AP reassociation since 0.6.5 Please try with current stable version and feel free to reopen if needed Thanks
