Comment 6 for bug 37120
Revision history for this message
| Andrew Jorgensen (ajorg) wrote Re: wpasupplicant doesn't work properly with rt2500 driver | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
It's not that it doesn't support WPA, it's that it doesn't support the wireless extensions used by wpasupplicant's wext driver. A wpasupplicant driver could be written to support the ioctls that rt2500 does use.
Another possibility is that wpasupplicant could be fixed to recognize what level of extensions are supported and fall back to only controlling the ssid. Or better yet, network-manager could recognize the problem and fall back to controlling the device directly.
In some reasonable way I'd love to see this fixed. I used to be able to use network-manager and now I can't (there's a bug elsewhere about network-manager not actually working without wpasupplicant like it claims it can).
In a later release, possibly dapper+1, we should be able to replace the rt2500 driver with the rt2x00 driver which does support the latest extensions. I can't test that driver right now because it requires kernel 2.6.16.