Walter, when you say you see no such issues are you using the -Dmadwifi or -Dwext with wpa_supplicant.
I have my Network Manager patched so it waits 60 seconds before deciding the link has timed out, however every 15-30 seconds wpa_supplicant scans, this I see using the -Dmadwifi driver. With -Dwext it is rock solid on my home wpa2 network. However at work -Dmadwifi is needed for leap/eap since -Dwext is unreliable for this type of connection. When you connect can you run "watch -n1 wpa_cli status" and see if it keeps dropping and scanning. I am kind of curious since I would love a solution/workaround for the scanning ...rescanning etc. Walter Neumann wrote: > I have no such problem with madwifi-ng-r2594-20070719. > > On Tue, 27 Nov 2007, Darren Albers wrote: > >> > On Tue, 2007-11-27 at 12:18 -0500, Philip A. Culver wrote: >> Hi, >> >> >> >> I am using NetworkManager 0.6.5 on Fedora 7 with the madwifi 0.9.3.3 >> drivers. I am experiencing an issue where NetworkManager thinks >> that the link has time out and shuts down the connection. It then >> tries to reconnect, which fails. At this point the device is >> deactivated. If I restart NetworkManager it usually reconnects >> immediately. >> >> >> My questions are as follows: >> >> >> >> * Is this a known issue with madwifi? If so does anyone know of any >> fixes for this? > > I have had similar issues with Athero's based cards and MadWifi. This > was the sole reason I selected a T61 over a Macbook this year. > I /think/ the reason for the disconnect is that Madwifi reports it's > signal strength differently than most other cards and therefore reports > significantly lower strength than other cards. So in one room of my > house if I am using an Intel 2200 B/G MiniPCI card I have 3 bars and a > stable connection, if I am using an IBM branded Atheros A/B/G MiniPCI > card I show one bar and get disconnected frequently. There was a hack > posted by Robert Love almost two years ago that "Translated" (If that is > the right way to describe it) the Madwifi signal reporting into a rough > approximation of what most cards use. This helped make the cards more > usable but still not enough to compare with other cards. > > I have been watching Ath5k development and I hope it will resolve these > issues since the author's won't be tied into working with a closed HAL. > In the meantime I would try and steer clear of Atheros based cards if > possible. > >> >> * Why is the device deactivated? Why wouldnÿÿt the device try to >> reconnect again after some period of time? Will I have to manually >> tell NetworkManager to reconnect? >> >> * I also experienced a crash in network manager in the same >> situation. >> >> >> I suspect my problems are perhaps related to madwifi but figured I >> would start here based on the crash and the fact that if I restart >> NetworkManager the connection is reestablished. >> >> >> >> I have included logs for both problems. >> >> >> Thanks, >> >> Phil >> >> >> >> Logs for deactivation and loss of link: >> >> Nov 27 11:22:22 localhost NetworkManager: <info> DHCP daemon state is >> now 3 (renew) for interface ath0 >> Nov 27 11:22:22 localhost dhclient: bound to 192.168.2.253 -- renewal >> in 142 seconds. >> >> Nov 27 11:24:44 localhost dhclient: DHCPREQUEST on ath0 to >> 192.168.2.55 port 67 >> >> Nov 27 11:24:44 localhost dhclient: DHCPACK from 192.168.2.55 >> >> Nov 27 11:24:44 localhost NetworkManager: <info> DHCP daemon state is >> now 3 (renew) for interface ath0 >> Nov 27 11:24:44 localhost dhclient: bound to 192.168.2.253 -- renewal >> in 119 seconds. >> >> Nov 27 11:26:35 localhost NetworkManager: <info> nm-netlink-monitor.c >> - nm_netlink_monitor_event_handler (724) netlink reports device ath0 >> link now 0 >> Nov 27 11:26:35 localhost NetworkManager: <info> nm-netlink-monitor.c >> - nm_netlink_monitor_event_handler (724) netlink reports device ath0 >> link now 0 >> Nov 27 11:26:43 localhost dhclient: DHCPREQUEST on ath0 to >> 192.168.2.55 port 67 >> >> Nov 27 11:26:51 localhost last message repeated 2 times >> >> Nov 27 11:26:55 localhost NetworkManager: <info> ath0: link timed >> out. >> Nov 27 11:26:55 localhost NetworkManager: <info> nm-device.c - >> nm_device_set_active_link (596) device ath0 link state set to 0 >> Nov 27 11:26:55 localhost NetworkManager: <info> SWITCH: found better >> connection 'ath0/GEM_RD_TEST' than current connection >> 'ath0/GEM_RD_TEST'. same_ssid=1, have_link=0 >> Nov 27 11:26:55 localhost NetworkManager: <info> Will activate >> connection 'ath0/GEM_RD_TEST'. >> Nov 27 11:26:55 localhost NetworkManager: <info> Device ath0 >> activation scheduled... >> Nov 27 11:26:55 localhost NetworkManager: <info> Deactivating device >> ath0. >> Nov 27 11:26:55 localhost dhclient: wifi0: unknown hardware address >> type 801 >> >> Nov 27 11:26:55 localhost dhclient: wifi0: unknown hardware address >> type 801 >> >> Nov 27 11:26:55 localhost dhclient: DHCPRELEASE on ath0 to >> 192.168.2.55 port 67 >> >> Nov 27 11:26:56 localhost avahi-daemon[1597]: Withdrawing address >> record for 192.168.2.253 on ath0. >> >> Nov 27 11:26:56 localhost avahi-daemon[1597]: Leaving mDNS multicast >> group on interface ath0.IPv4 with address 192.168.2.253. >> >> Nov 27 11:26:56 localhost avahi-daemon[1597]: Interface ath0.IPv4 no >> longer relevant for mDNS. >> >> Nov 27 11:26:56 localhost avahi-daemon[1597]: Withdrawing address >> record for fe80::240:96ff:feb5:68e on ath0. >> >> Nov 27 11:26:56 localhost avahi-daemon[1597]: Leaving mDNS multicast >> group on interface ath0.IPv6 with address fe80::240:96ff:feb5:68e. >> >> Nov 27 11:26:56 localhost avahi-daemon[1597]: Interface ath0.IPv6 no >> longer relevant for mDNS. >> >> Nov 27 11:26:56 localhost NetworkManager: <info> Activation (ath0) >> started... >> Nov 27 11:26:56 localhost NetworkManager: <info> Activation (ath0) >> Stage 1 of 5 (Device Prepare) scheduled... >> Nov 27 11:26:56 localhost NetworkManager: <info> Activation (ath0) >> Stage 1 of 5 (Device Prepare) started... >> Nov 27 11:26:56 localhost NetworkManager: <info> Activation (ath0) >> Stage 2 of 5 (Device Configure) scheduled... >> Nov 27 11:26:56 localhost NetworkManager: <info> Activation (ath0) >> Stage 1 of 5 (Device Prepare) complete. >> Nov 27 11:26:56 localhost NetworkManager: <info> Activation (ath0) >> Stage 2 of 5 (Device Configure) starting... >> Nov 27 11:26:56 localhost NetworkManager: <info> Activation >> (ath0/wireless): access point 'GEM_RD_TEST' is encrypted, and a key >> exists. No new key needed. >> Nov 27 11:26:56 localhost NetworkManager: <info> DHCP daemon state is >> now 14 (normal exit) for interface ath0 >> Nov 27 11:26:56 localhost NetworkManager: <info> DHCP daemon state is >> now 11 (unknown) for interface ath0 >> Nov 27 11:26:56 localhost NetworkManager: <info> DHCP daemon state is >> now 14 (normal exit) for interface ath0 >> Nov 27 11:26:57 localhost NetworkManager: <info> nm-netlink-monitor.c >> - nm_netlink_monitor_event_handler (724) netlink reports device ath0 >> link now 0 >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'INTERFACE_ADD ath0 wext /var/run/wpa_supplicant ' >> Nov 27 11:26:57 localhost NetworkManager: <info> nm-netlink-monitor.c >> - nm_netlink_monitor_event_handler (724) netlink reports device ath0 >> link now 0 >> Nov 27 11:26:57 localhost kernel: [57694.879957] ADDRCONF(NETDEV_UP): >> ath0: link is not ready >> >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'AP_SCAN 1' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'ADD_NETWORK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> '0' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'SET_NETWORK 0 ssid 47454d5f52445f54455354' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'SET_NETWORK 0 proto WPA' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'SET_NETWORK 0 key_mgmt WPA-EAP' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'SET_NETWORK 0 eap PEAP' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'SET_NETWORK 0 identity "pculver"' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'SET_NETWORK 0 password <password>' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'SET_NETWORK 0 anonymous_identity "pculver"' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'SET_NETWORK 0 pairwise TKIP' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'SET_NETWORK 0 group TKIP' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: sending command >> 'ENABLE_NETWORK 0' >> Nov 27 11:26:57 localhost NetworkManager: <info> SUP: response was >> 'OK' >> Nov 27 11:26:57 localhost NetworkManager: <info> Activation (ath0) >> Stage 2 of 5 (Device Configure) complete. >> Nov 27 11:27:11 localhost NetworkManager: <info> Old device 'ath0' >> activating, won't change. >> Nov 27 11:27:46 localhost last message repeated 2 times >> >> Nov 27 11:28:41 localhost last message repeated 3 times >> >> Nov 27 11:28:57 localhost NetworkManager: <info> Activation >> (ath0/wireless): association took too long (>120s), failing >> activation. >> Nov 27 11:28:57 localhost NetworkManager: <info> Activation (ath0) >> failure scheduled... >> Nov 27 11:28:57 localhost NetworkManager: <info> Activation (ath0) >> failed for access point (GEM_RD_TEST) >> Nov 27 11:28:57 localhost NetworkManager: <info> Activation (ath0) >> failed. >> Nov 27 11:28:57 localhost NetworkManager: <info> Deactivating device >> ath0. >> Nov 27 11:28:58 localhost NetworkManager: <info> nm-netlink-monitor.c >> - nm_netlink_monitor_event_handler (724) netlink reports device ath0 >> link now 0 >> Nov 27 11:28:58 localhost kernel: [57816.366814] ADDRCONF(NETDEV_UP): >> ath0: link is not ready >> >> Nov 27 11:28:58 localhost NetworkManager: <info> nm-netlink-monitor.c >> - nm_netlink_monitor_event_handler (724) netlink reports device ath0 >> link now 0 >> >> >> >> >> Backtrace logs >> >> Nov 27 05:39:48 localhost NetworkManager: <info> Activation (ath0) >> Stage 2 of 5 (Device Configure) complete. >> Nov 27 05:40:01 localhost NetworkManager: <info> Old device 'ath0' >> activating, won't change. >> Nov 27 05:40:37 localhost last message repeated 2 times >> >> Nov 27 05:41:31 localhost last message repeated 3 times >> >> Nov 27 05:41:47 localhost NetworkManager: <info> Activation >> (ath0/wireless): association took too long (>120s), failing >> activation. >> Nov 27 05:41:47 localhost NetworkManager: <info> Activation (ath0) >> failure scheduled... >> Nov 27 05:41:48 localhost NetworkManager: <info> Activation (ath0) >> failed for access point (GEM_RD_TEST) >> Nov 27 05:41:48 localhost NetworkManager: <info> Activation (ath0) >> failed. >> Nov 27 05:41:48 localhost NetworkManager: <info> Deactivating device >> ath0. >> Nov 27 05:41:49 localhost NetworkManager: <info> nm-netlink-monitor.c >> - nm_netlink_monitor_event_handler (724) netlink reports device ath0 >> link now 0 >> Nov 27 05:41:50 localhost NetworkManager: <WARN> nm_signal_handler(): >> Caught signal 11. Generating backtrace... >> Nov 27 05:41:50 localhost NetworkManager: ******************* START >> ********************************** >> >> Nov 27 05:41:50 localhost NetworkManager: Frame 0: NetworkManager >> [0x806d235] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame 1: NetworkManager >> [0x806d3e1] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame 2: [0x12d420] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame 3: >> NetworkManager(wpa_ctrl_request+0xb0) [0x80733b0] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame 4: >> NetworkManager(nm_utils_supplicant_request_with_check+0xda) >> [0x806acea] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame 5: NetworkManager >> [0x805be79] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame >> 6: /lib/libglib-2.0.so.0 [0x252dc6] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame >> 7: /lib/libglib-2.0.so.0(g_main_context_dispatch+0x182) [0x2527f2] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame >> 8: /lib/libglib-2.0.so.0 [0x2557cf] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame >> 9: /lib/libglib-2.0.so.0(g_main_loop_run+0x1a9) [0x255b79] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame 10: NetworkManager >> [0x80568de] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame >> 11: /lib/libglib-2.0.so.0 [0x27066f] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame >> 12: /lib/libpthread.so.0 [0x32444b] >> >> Nov 27 05:41:50 localhost NetworkManager: Frame >> 13: /lib/libc.so.6(clone+0x5e) [0x40780e] >> >> Nov 27 05:41:50 localhost NetworkManager: ******************* END >> ********************************** >> >> >> _______________________________________________ >> NetworkManager-list mailing list >> [email protected] >> http://mail.gnome.org/mailman/listinfo/networkmanager-list > > _______________________________________________ > NetworkManager-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ------------------------------------------------------------------------ > > _______________________________________________ > NetworkManager-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/networkmanager-list > _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
