So despite the broad cross-section of drivers being affected, Dan Williams on the networkmanager team still thinks this is a driver bug, and still thinks that periodic scanning is a good thing (completely ignoring the network lag it causes whenever a scan is done). See his followup:
http://mail.gnome.org/archives/networkmanager- list/2009-April/msg00301.html As I already stated in my previous message on the list, I've already spent as much time as I can afford on this, and I prefer the behavior with my patch to a NM that continues to invoke useless scans. If anyone else wants to try the NM_ACTIVE_AP_DEBUG test and report the results to the networkmanager list, please do. -- network-manager roams to (none) ((none)) https://bugs.launchpad.net/bugs/291760 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
