Hi Adam,
I’m trying to understand the the bgscan and autoscan parameters in plugins/wifi.c - specifically the maximum/long intervals of 300 seconds. With the supplicant’s default BSS Expiration Age of 180 seconds, this results in premature aging of the BSSs, resulting in an empty services list or perhaps worse, an inability to roam or recover from a lost association. I could always tweak these settings or increase the age in the supplicant - but I’m curious why I would need to change something like this out of the box - perhaps I’m missing something.
The point of autoscan is not to keep alive the list of BSS. It is to be able to find a service at some point, if you were moving around, while being disconnected. Scanning is expensive from power consumption point of view, thus an exponential delay with a limit of 300 seconds of automatic scanning. If you reach this limit of 300 seconds without being connected this means there is no know service around, so no need to pursue expensive scanning.
That said, this is relevant as long as you - as the user - do not request a scan by yourself. If you do so, this will reset the autoscan counter back.
About bgscan: this one is in use when you are connected, to roam if the AP setup supports it.
I may also ask the supplicant mailing list why they use these configurations in their examples as well, but I thought I’d start here.
autoscan is now connman-based only. As the wpa_supplicant's module does not handle hidden services. bgscan is ran in wpa_supplicant, the parameters we give are the default one which are usually ok. But it might depend on the wifi card and its driver (sometime the signal threshold is wrongly calculated there, so it only triggers when you are out of reach already)
Tomasz _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
