Hi,
I am actually working on some improvments to usteer and found a possible problem with hostapd. It seems that hostapd is kicking the clients on its own if disassociation timer is set. This brings in the problem that a rejection of the transition cannot be processed. Is there any way to stop the timer in hostapd if there really is one? I testet it manually with the following command.
ubus call hostapd.wl1-ap0 bss_transition_request '{"addr": "84:b1:e4:6e:xx:xx", "disassociation_imminent": true, "disassociation_timer": 1000, "validity_period": 100, "neighbors": ["60319733aac8ef0900005309070603010b00"], "abridged": true }'
Mon Nov 4 09:46:35 2024 daemon.notice hostapd: wl1-ap0: BSS-TM-RESP 84:b1:e4:6e:xx:xx status_code=7 bss_termination_delay=0
Mon Nov 4 09:46:35 2024 user.info usteer: Kick canceled because transition was rejected by sta=84:b1:e4:6e:xx:xx
Mon Nov 4 09:46:41 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Nov 4 09:46:43 2024 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Nov 4 09:46:47 2024 daemon.err uhttpd[1665]: [info] luci: accepted login on / for root from 192.168.177.109
Mon Nov 4 09:48:17 2024 daemon.notice hostapd: wl1-ap0: AP-STA-DISCONNECTED 84:b1:e4:6e:xx:xx
Mon Nov 4 09:48:17 2024 daemon.info hostapd: wl1-ap0: STA 84:b1:e4:6e:xx:xx IEEE 802.11: disassociated due to inactivity
Mon Nov 4 09:48:17 2024 user.info usteer: station 84:b1:e4:6e:xx:xx disconnected from node hostapd.wl1-ap0
Mon Nov 4 09:48:18 2024 daemon.info hostapd: wl1-ap0: STA 84:b1:e4:6e:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
UBUS MONITOR show this. Could this be triggered by hostapd itself?
[2024-11-04 10:03:36] <- 41b9ae52 #5245dee6 notify: {"objid":1380310758,"method":"disassoc","data":{"address":"84:b1:e4:6e:xx:x"},"no_reply":true}
[2024-11-04 10:03:36] -> 60d599b3 #41b9ae52 invoke: {"objid":1581435606,"method":"disassoc","data":{"address":"84:b1:e4:6e:xx:xx"},"no_reply":true,"user":"network","group":"network"}
Cheers,
Nils