AP: Reschedule ap_handle_timer event on (re)association
Previously, the timeout scheduled during the previous association was used after reassociation if the STA entry had not yet been removed. The next timeout does not need to happen that quickly, so reschedule it during reassociation. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
This commit is contained in:
parent
42ca9845be
commit
a625ff6059
1 changed files with 8 additions and 0 deletions
|
@ -990,4 +990,12 @@ void hostapd_new_assoc_sta(struct hostapd_data *hapd, struct sta_info *sta,
|
||||||
wpa_auth_sm_event(sta->wpa_sm, WPA_REAUTH);
|
wpa_auth_sm_event(sta->wpa_sm, WPA_REAUTH);
|
||||||
} else
|
} else
|
||||||
wpa_auth_sta_associated(hapd->wpa_auth, sta->wpa_sm);
|
wpa_auth_sta_associated(hapd->wpa_auth, sta->wpa_sm);
|
||||||
|
|
||||||
|
wpa_printf(MSG_DEBUG, "%s: reschedule ap_handle_timer timeout "
|
||||||
|
"for " MACSTR " (%d seconds - ap_max_inactivity)",
|
||||||
|
__func__, MAC2STR(sta->addr),
|
||||||
|
hapd->conf->ap_max_inactivity);
|
||||||
|
eloop_cancel_timeout(ap_handle_timer, hapd, sta);
|
||||||
|
eloop_register_timeout(hapd->conf->ap_max_inactivity, 0,
|
||||||
|
ap_handle_timer, hapd, sta);
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue