GNOME Bugzilla – Bug 632184
NM prevents authentication with WPAx-Enterprise
Last modified: 2012-08-22 19:56:34 UTC
Hi there! Problem: I've tried to connect to the Internet with my netbook (Asus EeePC 901) at different places, but I was unable to authenticate on networks using WPAx-Enterprise. All the access points belong to the well known network "eduroam". Workaround: Stop the network manager with "sudo stop network-manager" in order to prevent the wpa_supplicant daemon to restart. Then, create your own config file wpa_supplicant.conf and restart the daemon using it with "sudo wpa_supplicant -iwlan0 -cwpa_supplicant.conf". Ask for an IP, "sudo dhclient wlan0". The conf I use is (with the obvious changes): ctrl_interface=/var/run/wpa_supplicant eapol_version=1 network={ ssid="eduroam" proto=WPA key_mgmt=WPA-EAP eap=TTLS anonymous_identity="no_indentity" identity="my_identity" password="*******" phase2="auth=PAP" } Note: My system runs with Ubuntu 10.10 (up to date at this time). Note: some months ago, I had no problems (Ubuntu 10.04), but I started to notice it before upgrading to Maverick. Note: The bug has already been coroborate here: http://www.uluga.ubuntuforums.org/showthread.php?t=1595747
best thing to do is get a wpa_supplicant debugging log as described here: http://live.gnome.org/NetworkManager/Debugging under the "Debugging WiFi Connections" section. Then attach the /var/log/wpa_supplicant.log here so we can figure out what's going wrong. Thanks!
Created attachment 172439 [details] Debugging system logs On nm+wpa_fail.log: - I added "-dddt" at the exec line of /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service (which is also submitted) - Stopped NM, "sudo stop network-manager" - Killed wpa_supplicant, "sudo killall -TERM wpa_supplicant" - Restarted NM, "sudo start network-manager" - Filtered /var/log/daemon.log, "cat /var/log/daemon.log | grep -E '(NetworkManager|wpa_supplicant)' > nm+wpa_fail.log" - I must say that, surprisingly, I could browse the web for very few seconds (googled a word), but anything else. On wpa_success.log: - I stopped NM, "sudo stop network-manager" - Killed wpa_supplicant, "sudo killall -TERM wpa_supplicant" - Started wpa_supplicant with my own conf (see original post), "sudo wpa_supplicant -iwlan0 -cwpa_supplicant.conf -f wpa_success.log" - Requested an ip, "sudo dhclient wlan0" - When I finally got connection, I was able to navigate normally. On fi.epitest.hostap.WPASupplicant.service: - This is the original one. - wpa_supplicant is started with the modifier -s which is not documented. Note: I'm using Ubuntu Netbook Edition 10.10 on an Asus EeePC 901. The system sux a lot, so I'm considering to downgrade to 10.04.
network-manager-netbook is no longer being developed. However, the supplicant logs indicate AP-side problems, as the AP never replies. The e4:20 access point simply never replies the assocation requests from the driver, so the supplicant never gets to the actual EAP/authentication stuff. This looks like a wifi driver/kernel issue more than a supplicant issue.