Got around to updating my laptop today, and can confirm the fix. Works swimmingly on Gentoo, kernel 2.6.22. Thanks Jimmy.
On Mon, 27 Apr 2009, Jimmy C. Chau wrote:
As a follow-up to this, I like to note that this problem has been solved. The problem was apparently caused by wpa_supplicant-0.6.4, which was considered to be unstable by the upstream developers of wpa-supplicant, but was marked as stable on Gentoo. The solution is to upgrade to wpa_supplicant-0.6.9, which is currently the latest version that the upstream developers consider stable. For more information, see Gentoo bug #263633: <http://bugs.gentoo.org/show_bug.cgi?id=263633>. Thanks for everyone's help! -Jimmy Jimmy C. Chau wrote:In the process of furiously tweaking & reverting my configs, I noticed (through my wpa_gui window) that it somehow managed to connect and get an IP address. I ran a diff against my original wpa_supplicant.conf and realized that it was the same. In disbelief, I disconnected & reconnected & it still worked. Then I removed the debug flags from my /etc/conf.d/net for wpa_supplicant. Restart, & it gives me the same old CTRL-EVENT-EAP-STARTED EAP authentication started CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected CTRL-EVENT-EAP-FAILURE EAP authentication failed Since I strongly doubted that increasing the debug verbosity solved my problem, I decided to leave it running. Pages of the above message continued to appear. Sure enough, after a painfully long wait (long enough that it will probably be faster for me to go home, take a nap, grab a Ethernet cable & return to where I am), it was able to connect and acquire an DHCP lease. WPA: Key negotiation completed with 00:1b:d5:c9:6a:e2 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 00:1b:d5:c9:6a:e2 completed (reauth) [id=2 id_str=] So I downgraded back to 0.5.7 (the version I was using before), which is much faster in connecting (a few seconds), but has a worse wpa_gui interface than 0.6.4. I want to file a bug report so that this will get fixed, but I'm not sure what to report. I don't know what the problem is; nobody else online (that I can find) appears to have a similar problem; I don't know whether it's my configuration problem, the server's problem, or wpa_supplicant's problem; I don't even know what RADIUS server BU's using. Ryan, if you have time, can you try upgrading your wpa_supplicant to 0.6.4 to see whether it's just my computer? Anyone else who uses wpa_supplicant, please reply with its version number, your OS/distro, and whether it still works (you can get this with the following command): wpa_supplicant -v Thanks! Ryan Mullen wrote:Hi Jimmy and LUG, I am running Gentoo with a pretty old 2.6.22-suspend2-r2 kernel on my Acer laptop. I am using the onboard Atheros chipset wifi NIC with madwifi, lspci: 06:05.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01) I am using wpa_supplicant version 0.5.10. I can associate just fine to the 802.1x network, and my wpa_supplicant.conf snippet is here: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 ap_scan=1 network={ ssid="BU (802.1x)" priority=15 key_mgmt=WPA-EAP eap=PEAP MSCHAPV2 identity="rmullen" password="myBUpassword" phase2="auth=MSCHAPV2" } It's been this way ever since BU brought around 802.1x and you found they were assigning DHCP routes incorrectly. It's never stopped working. Let us know if this isn't enough to solve your problem. Ryan On Thu, 12 Feb 2009, Jimmy C. Chau wrote:Does anyone know or can anyone find out what RADIUS server BU is using for the "BU (802.1x)" wireless network? I'm having a bit of trouble getting it to work now (it appears to have stopped working within the past few weeks/month). There are quirks on certain servers that require the wpa_supplicant configuration to be slightly different depending on the RADIUS server used (attached is a table from the wpa_supplicant package about what works with what and how). Knowing what RADIUS server is being used (& if possible, the configuration used on that server) will make finding the correct configuration for wpa_supplicant much easier. BTW, has anyone else using Gentoo been having problems connecting to the "BU (802.1x)" network using wpa_supplicant? Is it still working for anyone else? Luke told me that it works on Ubuntu. I tried on one of the Ubuntu laptops in my lab: it doesn't connect. Thanks for any help. -- -Jimmy C. Chau <jchau@xxxxxx> <chaujc@xxxxxxxxx> GPG key ID: 0x8C6AA349 GPG key fingerprint: D889 2B2D E20F A07E 0D54 4280 9C14 D4F6 8C6A A349_________ BU LUG: http://lug.bu.edu. To unsubscribe, email bulug-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field.-- -Jimmy C. Chau <jchau@xxxxxx> <chaujc@xxxxxxxxx> GPG key ID: 0x8C6AA349 GPG key fingerprint: D889 2B2D E20F A07E 0D54 4280 9C14 D4F6 8C6A A349 _________ BU LUG: http://lug.bu.edu. To unsubscribe, email bulug-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field.
_________ BU LUG: http://lug.bu.edu. To unsubscribe, email bulug-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field.
