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>

diff --git a/wpa_supplicant/ctrl_iface.c b/wpa_supplicant/ctrl_iface.c
index b14c78f807d789061dc31912343508b4924b34f8..eb2d97d06f2cdb1a528dec2c59ddc16317b0b4d6 100644 (file)
--- a/wpa_supplicant/ctrl_iface.c
+++ b/wpa_supplicant/ctrl_iface.c
@@ -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);