© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Michael: Not sure if it's MSCHAPv2's problem, but according to aviv, the wireless router also plays an important role here. aviv's test result is, if the wireless router is changed to support TKIP or AES O.N.L.Y, then rt2860sta 1.8.0.0 + NM 0.7 works. My guess is if the wireless router only supports one key type, then the wifi driver won't have to figure it out itself so it can connect.
But unfortunately I can't change the company wifi router setting so I can't test aviv's finding.
Now I think I have a clearer picture of this issue. It's kind of a "mixed" problem:
(1) A flexible wifi router (which supports more than one key type) +
(2) A "stupid" wifi driver (which is not able to figure out the key type automatically) +
(3) NM 0.7 (which do not have the key type option to choose)
= NO WIFI !!
So aviv chose to fix (1) the router, you guys here chose to fix (2) downgrade the driver to 1.7.1.1, but I really want to choose (3) add this option in NM 0.7! Because you have to be award that this is not only a rt2860sta problem, a lot of other drivers out there have the same problem.