wpa_supplicant: Set state to DISCONNECTED on AP creation errors
If the AP creation failed (missing freq= or driver error) the supplicant would previously stay in SCANNING state forever. Instead, it should handle the error a bit better and drop back to DISCONNECTED so clients know something went wrong. Signed-hostap: Dan Williams <dcbw@redhat.com> intended-for: hostap-1
This commit is contained in:
parent
73a3c6ffca
commit
8c981d179b
1 changed files with 4 additions and 1 deletions
|
@ -1246,7 +1246,10 @@ void wpa_supplicant_associate(struct wpa_supplicant *wpa_s,
|
|||
"mode");
|
||||
return;
|
||||
}
|
||||
wpa_supplicant_create_ap(wpa_s, ssid);
|
||||
if (wpa_supplicant_create_ap(wpa_s, ssid) < 0) {
|
||||
wpa_supplicant_set_state(wpa_s, WPA_DISCONNECTED);
|
||||
return;
|
||||
}
|
||||
wpa_s->current_bss = bss;
|
||||
#else /* CONFIG_AP */
|
||||
wpa_msg(wpa_s, MSG_ERROR, "AP mode support not included in "
|
||||
|
|
Loading…
Reference in a new issue