Jouni Malinen <j@xxxxx> writes: > On Fri, Mar 19, 2010 at 10:56:37AM -0400, John W. Linville wrote: > >> If you can make wpa_supplicant scan less then I am sold! :-) > > I would assume it is not really wpa_supplicant that is triggering too > many scans for your liking, but NetworkManager.. Yes, I also believe that's the case. > The goal here (at least from my view point) is to actually make > wpa_supplicant itself trigger scans more frequently ;-). Heh, that's the finnish, pessimistic, way of answering to John's comment :) But as John is from US, we also have to use some optimism in the answer to not make him too nervous ;) So the aim is to to scan more when the connection is bad. But if the connection quality is good enough, wpa_supplicant would not scan at all. So in some cases scanning is more frequent and in some cases background scan is completely disabled. The ultimate goal is to reduce the background scan whenever we can, for example when connection is good or there's very little or no traffic at all. But we are nowhere near that yet. > wpa_supplicant already has a notification function just waiting to be > called from somewhere when a beacon is lost of signal strength has > changed.. That somewhere is supposed to be the driver event handler when > it receives one of these new roam trigger events. At that point, > wpa_supplicant can then figure out if it should start scanning more > frequently to find a better BSS. Very nice. > I would hope that this feature will make NetworkManager eventually > stop doing its constant scans I also hope that this will happen. I think the current setup is just one big layering violation. After the wifi connection is established, NetworkManager (nor Connection Manager) should not issue a scan unless requested by the user. > (or well, if it doesn't, I will provide an option in for > wpa_supplicant to ignore D-Bus requests for new scans.. ;-). That's also one way to do it. But let's hope that we can find a better solution. -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
