Call wpas_connection_failed() only if actually trying to connect
A disconnection event from the driver may end up getting delivered at a time when wpa_supplicant is not even trying to connect (e.g., during a scan that was already started after WPS provisioning step). In such a case, there is not much point calling wpas_connection_failed() and skipping this avoids confusing attempts of re-starting scanning while the previous scan is still in progress. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
This commit is contained in:
parent
f7da5a9ef4
commit
56d24b4ee0
1 changed files with 2 additions and 1 deletions
|
@ -1579,7 +1579,8 @@ static void wpa_supplicant_event_disassoc(struct wpa_supplicant *wpa_s,
|
|||
bssid = wpa_s->bssid;
|
||||
if (is_zero_ether_addr(bssid))
|
||||
bssid = wpa_s->pending_bssid;
|
||||
wpas_connection_failed(wpa_s, bssid);
|
||||
if (wpa_s->wpa_state >= WPA_AUTHENTICATING)
|
||||
wpas_connection_failed(wpa_s, bssid);
|
||||
wpa_sm_notify_disassoc(wpa_s->wpa);
|
||||
wpa_msg(wpa_s, MSG_INFO, WPA_EVENT_DISCONNECTED "bssid=" MACSTR
|
||||
" reason=%d",
|
||||
|
|
Loading…
Reference in a new issue