Cannot connect to 802.1x/PEAP/mschapv2 wireless network with rt2860

Sorry, forgot to mention that wpa_supplicant doesn't work also. The configuration file is the same as the one I used to connect my other laptop, so I'm positive it is correct.

Output from wpa_supplicant:
--------------------%<--------------------
Trying to associate with 00:13:19:c7:95:70 (SSID='eduroam' freq=2447 MHz)
Associated with 00:13:19:c7:95:70
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
OpenSSL: tls_connection_handshake - Failed to read possible Application Data error:00000000:lib(0):func(0):reason(0)
EAP-MSCHAPV2: Authentication succeeded
EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
CTRL-EVENT-CONNECTED - Connection to 00:13:19:c7:95:70 completed (auth) [id=0 id_str=]
--------------------%<--------------------

it just stays like that, No ip address, so I try to get one in another screen, which fails:

--------------------%<--------------------
$ sudo dhclient ra0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/ra0/00:21:85:b6:3f:af
Sending on LPF/ra0/00:21:85:b6:3f:af
Sending on Socket/fallback
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 10
--------------------%<--------------------

Hi,

It's been quiet here, is there anything I can do to get this checked out?

I understand that it's a very difficult thing to diagnose remotely, but I'm very motivated to get it resolved. Eduroam (the wireless network I want to connect to) is widely used in schools, research centers and universities worldwide.

Thanks,
Ger.

I have exactly the same problem here: I can't connect to any other network besides the ones using WEP key, WEP pre-shared key, WPA & WPA2 Personal and opened wireless networks.

Like Vorik I can't connect to any 802.1x/PEAP/mschapv2 wireless network.

My wireless Network adapter is intel pro/wireless 3945ABG, and I'm using the iwl3945 module version 1.2.26ks with the kernel 2.6.28-11-generic.

The fact that my ethernet adapter (RTL8111/8168B) was affected by the e1000e bug (basically it doesn't work anymore), this wireless problem affects me a lot.

Thanks for your assistance,

Cláudio

This is not a bug in the linux-meta package, moving to the linux package.

Apparently this problem was resolved just before the release of jaunty, at least for me.

Thanks for your assistance.

It still does not work for me. Note that Claudio's is another wireless card.

Thanks,
Ger.

At my university, they claim that only 8.10 (Intrepid) is able to connect successfully to our WEP 802.1x network.
(MSCHAPv2 + PEAP).

With 8.04 I got nothing. With 9.04 I get two green dots on Network Manager, but no authentication.

According to our IT dept., they've only managed with 8.10.

I'm running Ubuntu 9.04 NBR with eee-control package installed, on an eeepc 1000H. The kernel is the generic kernel that comes with 9.04 NBR

I've tried to use wicd with and config file that worked on my laptop with iwl3945. Wicd shows that it's connected to the university network successfully, but gateway is unreachable when it is pinged. So behavior of wicd is same as NetworkManager behavior.
Since Vorik failed to use wpa_supplicant, I stayed only one idea: try to update the driver.

I tried version 2.1.2.0, but nothing changed. NetworkManager connects to the university network but I cannot use the network. I asked system administrator what was happening on server side. He told me I was passing RADIUS authentication and then there were no network activity.
I managed to connect to network using ndiswrapper and the latest XP drivers, but it seems to be more unstable as compared with native driver.

I can confirm that my MSI Wind U100 with the RT2860 card, running Ubuntu 9.04, cannot connect to my WPA/WPA2 network with driver version 1.8.0.0 or 2.1.2.0.

I got it working by deleting the existing driver, and installing version 1.7.1.1, which I got here: http://www.array.org/ubuntu/dists/intrepid/eeepc/binary-i386/rt2860-dkms_1.7.1.1_all.deb

Yes, WPA/WPA2 personal does work with that driver, but not WPA2 Enterprise 802.1x/PEAP/mschapv2 with dynamic WEP..

It is still present in karmic. I was disappointed that no one can help to fix the bug within a year.
Maybe is it worth to fill bugreport at bugzilla.kernel.org?

I can confirm that my Asus Eee PC 1000H with the RT2860 card, running Ubuntu 9.10 cannot connect to 802.1x/PEAP/mschapv2. WEP works correctly. I really need to know the fix, because I can't connect to internet from my University.

I am also still unable to connect to PEAP/mschapv2. In my case I am seeing the following in my syslog:

Nov 18 09:37:35 my_laptop wpa_supplicant[1587]: TLS: Certificate verification failed, error 19 (self signed certificate in certificate chain) depth 2 for '/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority'
Nov 18 09:37:35 my_laptop wpa_supplicant[1587]: SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA

I don't actually know if this is the same or different cause as in jaunty (where I also could not connect to PEAP/mschapv2)

I've responded & posted more of my syslog at https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/293238/comments/3, but seen no response.

Regarding to the news(http://www.h-online.com/open/news/item/Kernel-Log-New-stable-kernels-2-6-33-with-DRBD-and-RT2800PCI-883212.html), kernel 2.6.33 will be shipped with new driver for rt2860. So I suggest ubuntu kernel team will backport the one to 2.6.31 or 2.6.32(in lucid). But it'll be not soon, because the driver is not ready.

I'm also affected by this on ubuntu netbook 10.04 on my asus EEE 1000. It would be so amazingly awesome if this could be fixed. I have been unable to connect to my university wireless for years now due to crappy wireless drivers. I'll try compiling the latest driver and see if it sucks less (honestly whoever made this chipset isn't able to make a decent driver after 2 YEARS?!? that's just ridiculous).

Kyle,
   Would you mind testing the .33 kernels, and possibly others? Information on doing this is available at: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds.

Thanks!

~JFo

also, Vorik or whomever,
   If there is an upstream bug on this somewhere, would you mind copying the link here or creating a bug watch for it?

Thanks!

~JFo

Major regression for me with 10.04. My Eee 1000 connected out of the box to my Belkin and DD-WRT WPA-secured routers under Easy Peasy, then 8.10 Netbook Remix, but it can't connect after the 10.04 upgrade.

I'm currently trying to find a way to get .33 installed. The mainline kernel packages do not contain the rt2860 driver.

I compiled vanilla 2.6.33.3 from source, and I'm able to connect to my WPA-secured network using the rt2860sta driver on my Eee 1000. The rt2800pci driver doesn't work, but the system prefers it over the staging driver and loads it automatically. I could've blacklisted it, but I just deleted rt2800pci.ko file from the /lib/modules tree instead.

I know a couple of other people affected by this bug who wouldn't be comfortable compiling their own kernels. It would be great to see this solved formally. What are the chances that a fix would make its way back into the 10.04 install ISO? Online updates aren't so helpful when you can't get online.

This works perfectly for my Asus eee1000. Good luck! http://ubuntuforums.org/showthread.php?t=1476007

I would just like to comment that the title of this thread is Cannot connect to 802.1x/PEAP/mschapv2 wireless network with rt2860. That being said, this issue still exists.

I have tried all of the methods across all of the postings and still cannot connect to a dynamic Wep 802.1x with PEAP authentication. It seems the ralink driver updates still is not working correctly with 802.1x. Now that being said yes WPA and WPA2 both work as does 128-WEP and no security (this is what i have been able to test), which i would say would work for most people however i think we need to stay on topic regarding the fact that Dynamic WEP 802.1X still does not work. If someone has a counter point to this, please post what you did to get this to work. Quite a few of us need this to work with Universities or Corporations that only offer this as a choice for wireless.

I have looked at the last official driver changelog(v2.4.0.0) and noticed a hopeful line inside it:
3. Fix issue: STA cannot connect to OPEN-WEP AP if WpaSupplicant set

Have anyone tried it?

Well connecting to PEAP/MSCHAPv2 networks work for me since I updated to Ubuntu 10.10, but I can't confirm directly if that's due to the changelog item you mention. I'm just pleased it works somehow, regardless :)

This bug is fixed by using the instructions located here:

http://ubuntuforums.org/showthread.php?t=1476007

I used the driver version 2.4.0.0 on Kubuntu 10.04 on an eeepc 901

Please note that the instructions in the above link include editing some of the flags in the driver before compilation. I suspect that these flag changes allow the new driver to work with WPA. The driver currently in the 10.04 repository does work on SOME wireless routers, but ONLY if the connection is not encrypted.

It would be wonderful if the devs could include the new driver in 10.04, which is an LTS version. At present, I have to keep copying the driver to new kernels as they get updated.

Thanks, guys.

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

I would certainly nominate it for Maverick, as I still have this problem there, but I don't see a "nominate" button anywhere.