Bugzilla – Bug 371571
NetworkManager does not connect anymore (madwifi?)
Last modified: 2008-03-17 13:35:11 UTC
I cannot connect with NetworkManager anymore since a few days. I have been applying the following patch to nm for some time to be able to connect: --- src/supplicant-manager/nm-supplicant-interface.c.orig 2008-01-20 +++ src/supplicant-manager/nm-supplicant-interface.c 2008-01-20 @@ -767,7 +767,7 @@ driver = g_new0 (GValue, 1); g_value_init (driver, G_TYPE_STRING); -g_value_set_string (driver, priv->is_wireless ? "wext" : "wired"); +g_value_set_string (driver, priv->is_wireless ? "madwifi" : "wired"); g_hash_table_insert (hash, "driver", driver); call = dbus_g_proxy_begin_call (proxy, With nm-0.6 I did not have to apply this patch. But somehow madwifi is not really wext-compliant. I opened a ticket at http://madwifi.org/ticket/1817. But now I have the following in the logs: <debug> [1205686570.926377] nm_system_device_get_system_config(): gw=0.0.0.0 <debug> [1205686570.926395] nm_system_device_get_system_config(): mask=0.0.0.0 <debug> [1205686570.926412] nm_system_device_get_system_config(): --------------------- <info> wlan0: Device is fully-supported using driver 'ath_pci'. <info> wlan0: driver does not support SSID scans (scan_capa 0x00). <info> Now managing wireless (802.11) device 'wlan0'. <info> Bringing up device wlan0 <info> Deactivating device wlan0. <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_17_f2_51_cf_ac_0 <info> Trying to start the supplicant... <info> Trying to start the supplicant... <info> Trying to start the supplicant... <info> Trying to start the supplicant... <info> Trying to start the supplicant... <info> Trying to start the supplicant... <info> Trying to start the supplicant... The message "wlan0: driver does not support SSID scans (scan_capa 0x00)." did not appear before.
wpa_supplicant seems to be involved in this too. Downgrading it to wpa_supplicant-0.5.8-82 (alpha2) solves the problem. I recompiled the src.rpm with wpa_supplicant-0.5.9 and that does not connect either as far as i can see. Therefore I think this one is for Helmut.
Felix, does your AP broadcast its SSID?
Yes it does. Here the iwlist output as reference: wlan0 Scan completed : Cell 01 - Address: 00:18:F8:B8:B6:24 ESSID:"freakshow" Mode:Master Frequency:2.437 GHz (Channel 6) Quality=24/70 Signal level=-71 dBm Noise level=-95 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s Extra:bcn_int=100 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK
Please try to connect using plain wpa_supplicant (0.5.10) with the option "-dd" to get verbose debug-output and attach it. Thanks.
Created attachment 202495 [details] wpa_supplicant -dd output Connecting with plain wpa_supplicant is not a problem. Nevertheless this is the output of # wpa_supplicant -Dmadwifi -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf -dd > wpalog.txt & and then starting wpa_gui to connect.
Does the configuration in wpa_supplicant.conf matches the one NetworkManager creates? Just compare it with the configuration NM sends to wpa_supplicant (relevant part of /var/log/NetworkManager).
wpa_supplicant.conf does not contain a lot of information: # cat /etc/wpa_supplicant/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel
Oops, you used wpa_gui. Missed that :) Could you please provide the output of wpa_supplicant in case of NetworkManager-connection-failure too? Just do the following: - rcnetwork stop - killall wpa_supplicant - wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -u -dd - rcnetwork start - connection attempt with NM
Helmut, it does work every time I start wpa_supplicant myself. Somehow NetworkManager seems unable to start wpa_supplicant-0.5.10 by itself for me. Watching ps aux there never appears a wpa_supplicant process... Can I somehow see how nm tries to invoke wpa_supplicant?
(In reply to comment #9 from Felix Möller) > Helmut, it does work every time I start wpa_supplicant myself. Somehow > NetworkManager seems unable to start wpa_supplicant-0.5.10 by itself for me. Ok, NetworkManager cannot start wpa_supplicant. Therefore closing as duplicate of #371500. *** This bug has been marked as a duplicate of bug 371500 ***