Don't disconnect on scan_freq update from control interface
It doesn't make sense to disconnect on updates to the network's scan_freq, and in fact doing so causes some (timing-/scheduling-dependent) test failures. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
This commit is contained in:
parent
dbcaf927cd
commit
b99bb32f55
1 changed files with 1 additions and 0 deletions
|
@ -3609,6 +3609,7 @@ static int wpa_supplicant_ctrl_iface_update_network(
|
|||
|
||||
if (os_strcmp(name, "bssid") != 0 &&
|
||||
os_strcmp(name, "bssid_hint") != 0 &&
|
||||
os_strcmp(name, "scan_freq") != 0 &&
|
||||
os_strcmp(name, "priority") != 0) {
|
||||
wpa_sm_pmksa_cache_flush(wpa_s->wpa, ssid);
|
||||
|
||||
|
|
Loading…
Reference in a new issue