mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-01-14 05:30:21 +01:00
wifi: fix evaluating the scanning state for wpa-supplicant
wpa_supplicant has a property "scanning" and a "state=scanning". Previously, NetworkManager considered both parts to indicate whether supplicant is currently scanning (if either the property or the state indicated scanning, it took that as indication for scanning). If NetworkManager thinks that supplicant is scanning, it suppresses explicit "Scan" requests. That alone is not severe, because the "Scan" request is only to trigger a scan in supplicant (which supplicant possibly is already doing in state "scanning"). However, what is severe is that NetworkManager will also block autoconnect while supplicant is scanning. That is because NetworkManager wants to get a complete scan result before deciding which network to connect to. It seems that wpa_supplicant can get into "state=scanning" and stay there indefinitely. This prevents NetworkManager from autoactivating a profile. Fix that, to only honor the "scanning" property. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/597 Fixes:b83f07916a('supplicant: large rework of wpa_supplicant handling') (cherry picked from commit8cadfed2fe) (cherry picked from commitfbe6240a7d)
This commit is contained in:
parent
a7dfcf076c
commit
2bec392e56
1 changed files with 1 additions and 2 deletions
|
|
@ -447,8 +447,7 @@ _notify_maybe_scanning (NMSupplicantInterface *self)
|
|||
gboolean scanning;
|
||||
|
||||
scanning = nm_supplicant_interface_state_is_operational (priv->state)
|
||||
&& ( priv->scanning_property
|
||||
|| priv->supp_state == NM_SUPPLICANT_INTERFACE_STATE_SCANNING);
|
||||
&& priv->scanning_property;
|
||||
|
||||
if (priv->scanning_cached == scanning)
|
||||
return;
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue