Bug 13217 - Standard Ralink driver RT2860 cannot connect to WPA2 networks
Summary: Standard Ralink driver RT2860 cannot connect to WPA2 networks
Status: CLOSED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-30 20:46 UTC by Bryan Stephenson
Modified: 2012-05-30 16:39 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.28-11
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Patch to correct WPA2 connection for driver RT2860 wifi chip (1.05 KB, patch)
2009-04-30 20:51 UTC, Bryan Stephenson
Details | Diff

Description Bryan Stephenson 2009-04-30 20:46:02 UTC
Overview:-
Wireless Cards using the popular RT2860 wifi chip manufactured by Ralink has not be able to connect to wireless access points and home routers that offer TKIP & AES encryption (i.e WPA2) after the release of driver 1.7.1.1.  This is the last driver that had WPA2 working. Current version on the Ralink driver is 2.1.1.0

Steps to reproduce:-
Use the kernal staging driver for the RT2860 in current release of kernel 2.6.28 or sonner. (kernel/drivers/staging/rt2860/rt2860sta.ko)  Cannot connect to a router with WPA2 (TKIP & AES)

Actual Results:-
Wpasupplcant cannot get past the 4 way handshaking process

Expected to be able to connect as it is stated as a feature.

OS:-
Ubuntu 9.04 @ stndard Jaunty build on 26/04/2009, (same problem occurs on opensuse as well)
Comment 1 Bryan Stephenson 2009-04-30 20:51:03 UTC
Created attachment 21175 [details]
Patch to correct WPA2 connection for driver RT2860 wifi chip
Comment 2 Bryan Stephenson 2009-04-30 20:53:55 UTC
please see Launchpad page for testing and background info

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/339891
Comment 3 Greg Kroah-Hartman 2009-04-30 22:31:26 UTC
Can you send me a patch against the kernel for this problem so that I can apply it with the proper attribution?
Comment 4 Bryan Stephenson 2009-05-01 12:35:22 UTC
Hi Greg could you explain in laymen terms what you need exactly as this is the first bug report I have filed.  how does the patch that is attached need to be modified or do you need to know more about the kernel version the patched source driver was build against?
Comment 5 Greg Kroah-Hartman 2009-05-01 15:41:15 UTC
On Fri, May 01, 2009 at 12:35:22PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> Hi Greg could you explain in laymen terms what you need exactly as this is
> the
> first bug report I have filed.  how does the patch that is attached need to
> be
> modified or do you need to know more about the kernel version the patched
> source driver was build against?

See the kernel file, Documentation/SubmittingPatches for everything that
you need to know about formatting the patch, documenting it, and how to
send it to me for inclusion.

If you have questions about this after reading the file, please let me
know.
Comment 6 Bryan Stephenson 2009-05-01 20:11:17 UTC
I have refered to the file and realised that the patch needed to be against the kernel itself and not the source driver as previous, I have redone it and sent it by mail to yourself and linux-wireless@vger.kernel.org. as this is my first go at this I expect it to be ripped apart!

if this is successful, how do we go about making Ralink adopt the change as well?  tried to email them but not had response
Comment 7 Greg Kroah-Hartman 2009-05-01 21:36:55 UTC
On Fri, May 01, 2009 at 08:11:17PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> if this is successful, how do we go about making Ralink adopt the change as
> well?  tried to email them but not had response

I have no idea, and it doesn't matter now that the driver is in the main
kernel tree.
Comment 8 T. J. Brumfield 2010-05-09 23:16:27 UTC
I ran into this myself while building a new rig and testing out openSUSE 11.3 beta. The card would not connect to a WPA2 network. I reinstalled openSUSE 11.2 with an older kernel, and it is working as expected now.

When I was Googling up the problem, I saw users running into this problem with every major distro. Has anyone tested this patch? And if it works, can we get it committed upstream?

Thanks!

Note You need to log in before you can comment on or make changes to this bug.