Re: rt2x00/rt2500 support

[Dan Williams <dcbw redhat com>]

On Tue, 2006-07-11 at 16:30 +1200, Eion Robb wrote:
> Hi there,
> 
> I've been testing the ralink rt2500 and rt2x00 drivers with NetworkManager  
> and I'm kind of frustrated with the NetworkManagerHardware wiki page.
> 
> RaLink rt2x00
> Provider:	http://rt2x00.serialmonkey.com
> Driver:	rt2x00
> Status:	Supports unencrypted and WEP networks when used with  
> NetworkManager. While the driver supports WPA, it does not use Linux  
> Wireless Extensions for WPA support, which is required for NetworkManager.

I just pulled the nightly CVS from here:
http://rt2x00.serialmonkey.com/wiki/index.php/Downloads

http://rt2x00.serialmonkey.com/rt2500-cvs-daily.tar.gz

for the rt2500.  I can find nowhere the driver actually supports WEXT.
I thought some bits of the rt2x00 driver used the devicescape 80211
stack, which means they _would_ actually support some stuff for WEXT.
But I can't find anywhere in the driver that does.

Furthermore, it doesn't look like the scan results function actually
returns the BSSID's WPA or RSN generic information element.  Which is
pretty much necessary.

> This is from the wiki page, but is very wrong.
> The legacy (ralink provided) rt2500/rt2400 drivers support unencrypted and  
> WEP networks and not WPA (with NetworkManager) as mentioned in the wiki
> The new (serialmonkey) rt2x00 drivers dont show anything up in the  
> nm-applet, as if it's not detected at all, and it _does_ use the wireless  
> extensions (works with wpa_supplicant -Dwext) for WPA.  In fact, looking  
> at the output of the NetworkManager daemon, it doesn't even blink an eye  
> when I load up the rt2x00 driver, but tells me I have a device when I load  
> up the rt2500 driver.

So if it does actually work for you with -Dwext for WPA, where did you
get the driver from?

Dan