I still believe scanning is a bad idea when you're already associated to an AP. I would guess in the cases where you're walking around a campus and the potential exists to roam between multiple equivalent APs, you could have a setting that says "scan when idle" or somesuch, e.g. when the screensaver activates. But in a lot of common cases, scanning while connected is just a waste.
I'd forgotten this bug report was here. I found that reverting this patch fixed it for me (ath9k)
commit 98f392b085985a7 5274fe02ec8aa92 f4ac0d8a80
Author: Dan Williams <email address hidden>
Date: Sat Oct 11 18:32:24 2008 +0000
2008-10-11 Dan Williams <email address hidden>
* src/nm- device- wifi.c
- (can_scan): remove old madwifi hack for not scanning while connected
And I had mentioned it here mail.gnome. org/archives/ networkmanager- list/2009- January/ msg00107. html
http://
but forgot about it afterward. Then at some point I wiped out my SVN tree and pulled the new NM source from git, and ran into the same problem all over again.
I still believe scanning is a bad idea when you're already associated to an AP. I would guess in the cases where you're walking around a campus and the potential exists to roam between multiple equivalent APs, you could have a setting that says "scan when idle" or somesuch, e.g. when the screensaver activates. But in a lot of common cases, scanning while connected is just a waste.