I tracked it down. Basically, disassociation doesn't occur properly. NM has incorrect disassociation logic, but because of how wpa_supplicant interacts it doesn't matter.
wpa_supplicant does an proper disassociation, but the ndiswrapper driver doesn't handle it properly. So, in short, it's a bug in ndiswrapper. It cannot use the NDIS disassociate, because it'll take down cards permanently in some cases. Therefore, they instead associate to an invalid AP and it doesn't take from paranoia logic in the driver. http://ndiswrapper.svn.sourceforge.net/viewvc/ndiswrapper/trunk/ndiswrapper/driver/iw_ndis.c?revision=2223&view=markup ** Changed in: network-manager (Ubuntu) Sourcepackagename: network-manager => ndiswrapper Status: Unconfirmed => Confirmed -- NetworkManager finds wireless network, does not connect https://launchpad.net/bugs/85468 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
