On Aug 17, 2017, at 2:37 AM, Jose Blanquicet
>> My 2¢: If "Active" scanning will indeed only return results for the
>> mentioned in the scan parameters, then I think ConnMan should *always*
>> schedule a passive scan afterwards, perhaps by just calling
>> wifi_scan_simple() in the scan_callback() of an active scan.
> That sounds reasonable. You should just take into account the timing, you
> cannot immediately ask wpa_supplicant for another scan because it could just
> be discarded due to there is another ongoing. That second passive scan needs
> to be done once you are sure the active scan has finished. You could try to
> implement this, I will think if this is the best we can do. Then we can test
> and discuss the options.
I was thinking and maybe this is not the best way to solve this issue.
The active scan is useful in order to perform a fast scan looking for the WiFi networks
we have got connected in the past. I think this is particularly helpful to speed up
auto-connect procedure at the start-up of the system. Instead, when user asks for scanning
I think it should always be a passive scan because users want to see all WiFi networks
available in range. Therefore, I propose to make ConnMan ask wpa_supplicant for an active
scan only at star-up of the system and passive scan when it is directly asked from users
through a Technology.Scan() D-Bus call. Both things no matter BackgroundScanning's
What do all you think?
(Now it was my turn to be on vacation! Sorry for the delay.)
Great idea. This is fine for my use case, and the behavior you propose is what I expected
given what Technology.Scan() claims to do.