We have several options from here:
1.) Fix network-manager to use the rt2500 supplicant
2.) fix rt2500 to implement WE19 fully so wpasupplicant can be used with 'wext' driver backend.
3.) implement support for private rt2500 ioctls in both rt2500 and wpasupplicant
Option 3 is very likely to be rejected by wpasupplicant upstream, and I assume by rt2500 upstream as well, we shouldn't go that way.
I don't know how much work option 1 would be, and I consider Option 2 as the only feasible long term option.
No, it is a rt2500 driver problem. It doesn't want to be used with wpasupplicant at all, because it seems to bring in an own supplicant in kernel-space: /wiki.ubuntu. com/WifiDocs/ RalinkRT2500? action= show&redirect= Rt2500WirelessC ardsHowTo
https:/
We have several options from here:
1.) Fix network-manager to use the rt2500 supplicant
2.) fix rt2500 to implement WE19 fully so wpasupplicant can be used with 'wext' driver backend.
3.) implement support for private rt2500 ioctls in both rt2500 and wpasupplicant
Option 3 is very likely to be rejected by wpasupplicant upstream, and I assume by rt2500 upstream as well, we shouldn't go that way.
I don't know how much work option 1 would be, and I consider Option 2 as the only feasible long term option.