On Fri, Dec 13, 2024 at 07:56:29PM +0200, Jussi Laakkonen wrote: > Some drivers do start scheduled scan but never finish with the results. > This timeout is equal to the scan timeout and behaves similarly, except > the scan stopped event is sent when timeout is reached. > > Timeout will be started when the scheduled scan is initiated and > canceled when the scan is stopped. Timeout itself is calculated > similarly to the scan event timeout, ranging from 10s to 30s and for > this a separate wpa_driver_nl80211_get_scan_timeout() is created to > avoid code duplication. I would really prefer not to have to do something like this in wpa_supplicant. The "normal scan" case was a known issue with various drivers misbehaving and a workaround being justified, but scheduled scan was a much more recent addition especially as an nl80211 command/event (instead of some vendor specific interfaces) and it should have been implemented correctly in the drivers and if not, the drivers should be fixed instead of making this more complex for user space. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
