AP: Reset STA timeout_next on driver-based-SME association
The next ap_handle_timer action was already cleared when association is handled with user space -based SME. However, this step was missing from the driver callback for indicating new association. This could result in the first ap_handle_timer timeout on the new association removing the station unexpectedly. Fix this by resetting the timeout_next in hostapd_notif_assoc(). Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com> intended-for: hostap-1
This commit is contained in:
parent
31b4961f02
commit
c72bd6d49b
1 changed files with 6 additions and 0 deletions
|
@ -78,6 +78,12 @@ int hostapd_notif_assoc(struct hostapd_data *hapd, const u8 *addr,
|
||||||
sta = ap_get_sta(hapd, addr);
|
sta = ap_get_sta(hapd, addr);
|
||||||
if (sta) {
|
if (sta) {
|
||||||
accounting_sta_stop(hapd, sta);
|
accounting_sta_stop(hapd, sta);
|
||||||
|
|
||||||
|
/*
|
||||||
|
* Make sure that the previously registered inactivity timer
|
||||||
|
* will not remove the STA immediately.
|
||||||
|
*/
|
||||||
|
sta->timeout_next = STA_NULLFUNC;
|
||||||
} else {
|
} else {
|
||||||
sta = ap_sta_add(hapd, addr);
|
sta = ap_sta_add(hapd, addr);
|
||||||
if (sta == NULL)
|
if (sta == NULL)
|
||||||
|
|
Loading…
Reference in a new issue