On Sat, Oct 03, 2020 at 10:04:36AM -0500, KeithG wrote:
After I finally, painfully, figured this out and can get the wifi to
reconnect when the SSID radio goes down then comes back up. So I am running
and I notice a lot of log spam where it is now scanning the ethernet port
even though the wifi is connected. I believe this is because I now have
'BackgroundScanning=true' and have the default of
'SingleConnectedTechnology = false'.
BackGroundScanning is only relevant for the wpa_supplicant plugin
(plugins/wifi.c). iwd is able to steer the scanning itself and doesn't
need ConnMan to tell how to scan. You can still trigger a manual scan
but this is not needed in general. It's just if you have an impatient
user who doesn't want to wait for the regular scan.
I have a question, though, would it be reasonable if the
flag could be = true,ethernet,wifi,bluetooth as opposed to just =
BackgroundScanning is really only for the wpa_supplicant plugin. It's
very unfortunate that ConnMan even has to know about it. It's a layer
I ask as I can imagine that there would be a situation where a
user would want the bt or wifi to scan if it became disconnected, but the
ethernet port can be easily unplugged/replugged to trigger a
For this we have the manual scan.