Is wpa_supplicant needed for WPA2PSK with latest rt73 CVS?

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=3038

xjerky

29-01-2007 12:29:13

I've been wracking my brain all weekend, trying to get this to work, and I feel like I'm getting conflicting, outdated suggestions when I google around...so I figured I'd ask straight from the source.

The rt73 module loads and with 'iwlist scan' I can see available networks, so I believe I got someplace, at least.

(And btw, do I still need to copy firmware and dat files to /etc/Wireless/RT73STA/ ? The README file from CVS makes no mention of it, and I figure if I'm able to scan networks, then the device is functional without loading the seperate firmware file)

But when I try to use wpa_supplicant I get this error

# /usr/local/bin/wpa_supplicant -Dwext -irausb0 -c/etc/wpa_supplicant/wpa_supplicant.conf -dd

WEXT Operstate linkmode=1, operstate=5
Own MAC address 001478788505
wpa_driver_wext_set_wpa
ioctl[SIOCSIWAUTH] Operation not supported
WEXT auth param 7 value 0x1 - Driver does not support WPA.
wpa_driver_wext_set_key alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT] Operation not supported

And a whole bunch of other errors, but I figure the WPA support not being there makes posting all of the rest pointless.

If It helps, I'm using an Apple Airport Express, which supports WPA2 and AES.

And help would be greatly appreciated!

Spy84464

29-01-2007 13:56:53

Hello,
wpa-supplicant doesn't work with the legacy rt73 driver. It does support WPA nevertheless, you need to use "iwpriv" to configure your stick. The "iwpriv_usage.txt" file coming with the driver contains the details.

Regards,
Romain

firefly

29-01-2007 18:15:00

Hello,
wpa-supplicant doesn't work with the legacy rt73 driver. It does support WPA nevertheless, you need to use "iwpriv" to configure your stick. The "iwpriv_usage.txt" file coming with the driver contains the details.

Regards,
Romain[/quote145rk64v]
wpa_supplicant does work, at least with WEP and ap_scan=2(hidden ESSID)

Spy84464

30-01-2007 15:22:04

It should work with WEP indeed, but there isn't much point in using wpa_supplicant for WEP, unless you need any 802.1X authentication. I don't know if it's possible to use such authentication with rt61 legacy though.

firefly

30-01-2007 17:15:39

i forgot to say that also WPA-PSK works with the rt73 legacy driver an wpa_supplicant

Spy84464

31-01-2007 12:38:13

That's because you are using Ralink's wpa-supplicant driver firefly ;).

firefly

31-01-2007 12:55:50

That's because you are using Ralink's wpa-supplicant driver firefly ;).[/quote2ko6oku6]
yeah ;) because the legacy rt73 driver is not yet compatible to the wext wpa_supplicant driver ;)

EDIT
I have added the patch for the ralink wpa_supplicant driver. It applies cleanly against the v0.5.7 version of wpa_supplicant. It is the original code from ralink i have only adapted it to the changes of the ioctl handling in the rt73 driver.

deej

10-03-2007 22:23:25

That's because you are using Ralink's wpa-supplicant driver firefly ;).[/quote267xnjwh]
yeah ;) because the legacy rt73 driver is not yet compatible to the wext wpa_supplicant driver ;)

EDIT
I have added the patch for the ralink wpa_supplicant driver. It applies cleanly against the v0.5.7 version of wpa_supplicant. It is the original code from ralink i have only adapted it to the changes of the ioctl handling in the rt73 driver.[/quote267xnjwh]

I'm using Ubuntu Edgy, would this also patch against the supplied wpa_supplicant 0.5.4 in Edgy? I tried downloading the 0.5.7 source but it refuses to compile with loads of errors (.

Right now I'm using ndiswrapper to get the wpa working (and wpa2 doesn't work for an rt2561w I think).

EDIT did a apt-get source wpasupplicant, patch -i ralink.patch and behold, it compiles and works (well, sort of). When using wpa_supplicant with ndiswrapper drivers I can associate to a WPA AP (not WPA2), with the ralink driver (and patch) it continously spits out "Custom wireless event receive DISASSOCIATED_EVENT !!!", which is added by the ralink patch it appears.

geis

02-07-2007 18:45:56

I'm having some issues with wpa_supplicant interfacing with rt73 including the driver_ralink.[ch] patch. I had to change some pointer arithmetic to get it to work with PSK (or at all, really -- see last paragraph below). Now I'm having an issue with EAP not working and before I go ripping through wpa_supplicant code again, I was hoping to get some direction about the rt73 driver.

I guess the bottom line question is, does EAP support from wpa_supplicant require the driver do anything? I.e., when we say rt73 supports WEP, and WPA-PSK, are we saying it isn't capable of properly relaying EAP packets, or simply that native support isn't in the driver for EAP?

The wpa_supplicant issue I had was on an ARM processor, BTW. I'm not sure if it's related to that or not, but the OID_802_11_BSSID_LIST - returned (I just hyphenated a #define to make a new English word) structures had an off-by-three error. I haven't had the chance to dig through why that's happening, but I'm assuming it's a structure issue between the user-space stuff and kernel space stuff. I can provide more info if anyone is actually interested ;-)

Thanks,
geis

anarxisco

08-11-2007 22:42:35


EDIT
I have added the patch for the ralink wpa_supplicant driver. It applies cleanly against the v0.5.7 version of wpa_supplicant. It is the original code from ralink i have only adapted it to the changes of the ioctl handling in the rt73 driver.[/quote3at8ap4d]

Hi,
this pathc works with latest version of wpa_supplicant 0.6.0?

thanks

Starcrasher

09-11-2007 23:09:03

Unfortunately, I don't think it can apply anymore since a driver for ralink devices (using the Ralink driver) has already been included in wpa_supplicant package.
I have no idea, if there is a lot of differences with the driver contained in the original Ralink patch.
But, if someone modify the patch or create a new one, it will surely help a lot of people.

Spy84464

10-11-2007 11:10:20

That shouldn't be a problem, it's only a numeric value to change. Note that you could also patch the driver, but that would break RutilT support, unless you patch it as well!