Okay so to answer some of my own questions... It appears that the change to AP_SCAN 1 for hidden networks was deliberate, but this very change is exactly what broke NetworkManager + ndiswrapper. I've attached a patch that checks for ndiswrapper and uses AP_SCAN 2 if it finds it. Unfortunately it still does not fix hidden network auto-detection, but at least you can connect to hidden networks using the "Connect to Other Wireless Networks..." option... which you couldn't do with -15, -16, or -16.7.10.0 using ndiswrapper.
Which leads me to a very irritating point... Mark Ferguson's post on 10/23 pointed out that there was a problem with Alexander Sack's patch, which totally broke ndiswrapper with hidden networks. Mark described exactly what the problem was and exactly what was needed to fix it (change AP_SCAN 1 to AP_SCAN 2 for ndiswrapper). Over two months later, being frustrated that the problem is going unnoticed, having never modified a Debian package before or even looked at the source for NetworkManager, ndiswrapper, or wpa_supplicant before...I was able to come up with a patch for this in a matter of hours. I think anyone who had been working with this code could probably have done this in five minutes. I hate to be complaining, and I know that this is a community project and is enhanced by people in their spare time and all that stuff... but seriously guys... what is going on? network-manager is a rather significant package that has become central to Ubuntu's functionality. And the Broadcom chipset is not uncommon at all (look in Dell laptops, Linksys wireless adapters, etc...). ** Attachment added: "fix_hidden_ndiswrapper.patch" http://launchpadlibrarian.net/11087999/fix_hidden_ndiswrapper.patch -- can't connect to hidden network https://bugs.launchpad.net/bugs/50214 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
