+1
according to https://openwrt.org/releases/21.02/notes-21.02.0-rc1 WPA3 support is by default part of 21.xx, so would be good to know if wpad-openssl is still really a dependency, or what is missing in recent default wpad base package may used by dawn?
1 Like
The rrm part (as far as I know).
1 Like
Do this test from my post above. Different wpad versions don't have the same set of methods, and without the DISASSOCIATE one (part of 802.11v) DAWN can't kick the device.
1 Like
- you mean
this is not enough:
Summary
opkg list-installed | grep wpad; ubus -v list hostapd.wlan5-1
wpad-basic-wolfssl - 2020-06-08-5a8b3662-35
'hostapd.wlan5-1' @eb8e1c98
"reload":{}
"get_clients":{}
"get_status":{}
"del_client":{"addr":"String","reason":"Integer","deauth":"Boolean","ban_time":"Integer"}
"list_bans":{}
"update_beacon":{}
"get_features":{}
"switch_chan":{"freq":"Integer","bcn_count":"Integer","center_freq1":"Integer","center_freq2":"Integer","bandwidth":"Integer","sec_channel_offset":"Integer","ht":"Boolean","vht":"Boolean","block_tx":"Boolean"}
"set_vendor_elements":{"vendor_elements":"String"}
"notify_response":{"notify_response":"Integer"}
"bss_mgmt_enable":{"neighbor_report":"Boolean","beacon_report":"Boolean"}
"rrm_nr_get_own":{}
"rrm_nr_list":{}
"rrm_nr_set":{"list":"Array"}
"rrm_beacon_req":{"addr":"String","mode":"Integer","op_class":"Integer","channel":"Integer","duration":"Integer","bssid":"String","ssid":"String"}
but this is ok:
Summary
opkg list-installed | grep wpad; ubus -v list hostapd.wlan5-1
wpad-wolfssl - 2020-06-08-5a8b3662-35
'hostapd.wlan5-1' @8d36a484
"reload":{}
"get_clients":{}
"get_status":{}
"del_client":{"addr":"String","reason":"Integer","deauth":"Boolean","ban_time":"Integer"}
"list_bans":{}
"wps_start":{}
"wps_status":{}
"wps_cancel":{}
"update_beacon":{}
"get_features":{}
"switch_chan":{"freq":"Integer","bcn_count":"Integer","center_freq1":"Integer","center_freq2":"Integer","bandwidth":"Integer","sec_channel_offset":"Integer","ht":"Boolean","vht":"Boolean","block_tx":"Boolean"}
"set_vendor_elements":{"vendor_elements":"String"}
"notify_response":{"notify_response":"Integer"}
"bss_mgmt_enable":{"neighbor_report":"Boolean","beacon_report":"Boolean","bss_transition":"Boolean"}
"rrm_nr_get_own":{}
"rrm_nr_list":{}
"rrm_nr_set":{"list":"Array"}
"rrm_beacon_req":{"addr":"String","mode":"Integer","op_class":"Integer","channel":"Integer","duration":"Integer","bssid":"String","ssid":"String"}
"wnm_disassoc_imminent":{"addr":"String","duration":"Integer","neighbors":"Array","abridged":"Boolean"}
- why is dependency on openssl? wpad-wolfssl lacks something? as wpad-basic-wolfssl is the default in base.
1 Like
1: Yes re the two outputs you included.
2: I'm not sure anyone has stated a dependency on openssl. It was just an example of a non-basic package that works. I'll adjust the install wording to be clear that anything providing wnm_disassoc_imminent is OK. If you / others want to propose what it can be I'll add that too.
1 Like
i wander if there are some recomendation for /etc/config/wireless i configered it long ago before i start to test DAWN
so here it is my wireless
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option path 'platform/10180000.wmac'
option channel '1'
option cell_density '0'
option country 'RU'
option beacon_int '50'
option log_level '1'
option distance '10'
option txpower '7'
option htmode 'HT40'
config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'psk2'
option key '1225612256'
option ieee80211r '1'
option mobility_domain '8888'
option ft_psk_generate_local '1'
option ft_over_ds '0'
option rrm_neighbor_report '1'
option rrm_beacon_report '1'
option bss_transition '1'
option na_mcast_to_ucast '1'
option time_advertisement '2'
option ieee80211k '1'
option nasid ' 78A3517BFA54'
May it be some parametrs in wireless will badly affect DAWN work?
sorry i meant openssl version of wpad , a.k.a. wpad-openssl as the installation manual states see. so the only requirement from dawn point of view is to have full version of wpad, be it WPA3 supported *ssl version or not.
on my hw version i can see these packages at this moment:
Summary
opkg list wpad* | awk '{print $1}'
wpad
wpad-basic
wpad-basic-openssl
wpad-basic-wolfssl
wpad-mesh-openssl
wpad-mesh-wolfssl
wpad-mini
wpad-openssl
wpad-wolfssl
from this list wpad, wpad-wolfssl, wpad-openssl equally fine but others are not, do i understand correctly?
1 Like
The standard packages are called wpad-basic-wolfssl and wpad-basic-openssl. They are not enough.
1 Like
Nothing there will directly affect DAWN AFAIK. As discussed above (I think...), having 802.11r working is generally a good thing if you want thing to roam more often, but not necessary.
1 Like
Hi All, I've moved from a proprietary mesh using TP Link deco's to a pair of RT3200's. All good so far, and the extra options I have now are like nectar to a hungry bee.
I was having problem with clients moving between AP's, and DAWN has solved that, things working very well on the main 'mesh' SSID. I have a pair of secondary hidden SSID's to be able to force a device to one or other of the AP's, but normally nothing would be connected to the SSID's.
I've got 80211.vkr options enabled and full WPAD installed, and I can see stations hopping and moving around the network, from 2.4 to 5 and from AP1 to AP2. So functionally all good.
In the logs on both the AP, and the main router I see however warnings from DAWN
Fri Feb 11 21:32:08 2022 daemon.warn dawn[9975]: No station connected
Obviously I can disable logging, but where is the error coming from, is it because I've hidden SSID's that no client should be using unless I manually connect, or is there something else?
I ve been testing dawn with diffrent parametrs lately and still cant get normal kicking even though i set up kicking in more aggresive way than by default
option kicking_threshold '10' # diffrence in Db beetwin 2 APs to perform kicking
option rssi_val '-63' # level is good to connect
option low_rssi_val '-73' #bad level lower level performs kicking
option bandwidth_threshold '64' # lower than 64 Mbits allows to kick client
option kicking '1'
option set_hostapd_nr '2'
option min_number_to_kick '1'
still cant see kicking when signall is lower -73Db and speed of use lower than 64 Mbits/s
i use wifiman to see the roaming and even if i have -77Db (for 1 minute) still connected to the APs
it feels like what ever i put in dawn config there is no diffrence in behavior
I need config that would be real agressive like it is -73 Db for 1 sec kick no mater what
That's a message at the wrong level of reporting, it should probably be for tracing not warning.
It simply means that one of the BSSID has no clients. For example, if all clients were on the 5GHz radio you would see that message for the 2.4GHz BSSID.
So yes, your hidden SSID are likely to cause that.
2 Likes
If you use ubus call dawn get_hearing_map what does it show for a client you think should be moving?
1 Like
0E:46:FF:CD:9F:C0 is the divice that moves
68:15:90:E7:59:FC and F8:5E:3C:0C:59:10 2 APs
root@33:~# ubus call dawn get_hearing_map
{
"Open22Wrt": {
"0E:46:FF:CD:9F:C0": {
"68:15:90:E7:59:FC": {
"signal": -47,
"rcpi": -1,
"rsni": -1,
"freq": 2462,
"ht_capabilities": false,
"vht_capabilities": false,
"channel_utilization": 0,
"num_sta": 1,
"ht_support": false,
"vht_support": false,
"score": -2
},
"F8:5E:3C:0C:59:10": {
"signal": -74,
"rcpi": -1,
"rsni": -1,
"freq": 2437,
"ht_capabilities": true,
"vht_capabilities": true,
"channel_utilization": 11,
"num_sta": 1,
"ht_support": true,
"vht_support": false,
"score": -2
}
},
"AC:3C:0B:6B:3A:5D": {
"F8:5E:3C:0C:59:10": {
"signal": -92,
"rcpi": -1,
"rsni": -1,
"freq": 2437,
"ht_capabilities": true,
"vht_capabilities": false,
"channel_utilization": 11,
"num_sta": 1,
"ht_support": true,
"vht_support": false,
"score": -2
}
}
}
}
i am standing 0.5Meters away client 0E:46:FF:CD:9F:C0 connected to far AP with -75 -85 from AP and log shows
Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
or i should place the phone in the place where it supposed to be kicked ant that moment?
That is not a useful score to compare between APs. We'll have to work out why it is reached.
1 Like
Once we have positive numbers for each device they can be compared, but somehting is dominating the score and making it negative (which is then "rounded" to -2 as a general indicator of a very low score).
Do you have anything under the config metric '802_11g' section, and if so can you share them as it might explain what is happening?
Putting the following two entries in that section in might lift the score from -2.
option initial_score '80'
option max_chan_util '-10'
EDIT: Also just spotted that the rssi_val and low_rssi_val entries should be in that band specific section. They didn't used to be, so the example / default configs can be misleading.
1 Like
I have been trying to acchive agressive kiking latly so i screw the config blindlessly and deleted the
config metric '802_11g' thought the 'global' take care about '802_11g'
now i edited /etc/config/dawn
and it is
config network
option broadcast_ip '192.168.222.255'
option broadcast_port '1025'
option tcp_port '1026'
option network_option '2'
option shared_key 'Niiiiiiiiiiiiick'
option iv 'Niiiiiiiiiiiiick'
option use_symm_enc '0'
option collision_domain '-1'
option bandwidth '-1'
config ordering
option sort_order 'cbfs'
config hostapd
option hostapd_dir '/var/run/hostapd'
config times
option update_client '10'
option denied_req_threshold '30'
option remove_client '15'
option remove_probe '30'
option remove_ap '460'
option update_hostapd '10'
option update_tcp_con '10'
option update_chan_util '5'
option update_beacon_reports '600'
config metric 'global'
option rssi_weight '2'
option rssi_center '0'
option initial_score '0'
option kicking_threshold '10'
option duration '600'
option rrm_mode 'apt'
option ap_weight '0'
option ht_support '0'
option vht_support '0'
option no_ht_support '0'
option no_vht_support '0'
option rssi '0'
option low_rssi '0'
option freq '0'
option chan_util '0'
option max_chan_util '0'
option rssi_val '-60'
option low_rssi_val '-70' #changed to -70Db
option chan_util_val '0'
option max_chan_util_val '0'
option min_probe_count '0'
option bandwidth_threshold '128'
option use_station_count '0'
option max_station_diff '0'
option eval_probe_req '0'
option eval_auth_req '0'
option eval_assoc_req '0'
option kicking '1'
option deny_auth_reason '1'
option deny_assoc_reason '17'
option use_driver_recog '1'
option chan_util_avg_period '3'
option set_hostapd_nr '1'
option min_number_to_kick '1'
config metric '802_11g'
option rssi_weight '2'
option rssi_center '-60'
option initial_score '80'
option max_chan_util_val '-10'
config local
option loglevel '1'
And ubus call dawn get_hearing_map :
"0E:46:FF:CD:9F:C0": {
"68:15:90:E7:59:FC": {
"signal": -50,
"rcpi": -1,
"rsni": -1,
"freq": 2462,
"ht_capabilities": false,
"vht_capabilities": false,
"channel_utilization": 0,
"num_sta": 1,
"ht_support": false,
"vht_support": false,
"score": 116
},
"F8:5E:3C:0C:59:10": {
"signal": -88,
"rcpi": -1,
"rsni": -1,
"freq": 2437,
"ht_capabilities": true,
"vht_capabilities": true,
"channel_utilization": 7,
"num_sta": 2,
"ht_support": true,
"vht_support": false,
"score": 40
}
},
and now i see kicking in the log
0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 43.299999
But it looks like kicking performing not at the level -70Db but -80Db
so there are few parametrs for kikcking :
config metric 'global'
option kicking_threshold '10'
option bandwidth_threshold '128'
option rssi_val '-60'
option low_rssi_val '-70'
config metric '802_11g'
option rssi_weight '2'
option rssi_center '-60'
option initial_score '80'
option max_chan_util_val '-10'
what else can i change for making it kicking on level -71Db
A few parameters have ended up in the wrong section there, and by not specifying the "stepped" RSSI parameters for 802_11g they would have been defaulting to non-zero and "fighting" with the weighted values you did specify.
Please try this to see if it does what you want. Delete your sections with the same name and paste these in. No need to change the other sections.
config metric 'global'
option kicking '1'
option kicking_threshold '10'
option min_number_to_kick '1'
option use_station_count '0'
option max_station_diff '0'
option bandwidth_threshold '128'
option rrm_mode 'apt'
option set_hostapd_nr '1'
option duration '600'
option chan_util_avg_period '3'
option eval_probe_req '0'
option min_probe_count '0'
option eval_auth_req '0'
option deny_auth_reason '1'
option eval_assoc_req '0'
option deny_assoc_reason '17'
config metric '802_11g'
option initial_score '80'
option rssi_val '-60'
option rssi '0'
option low_rssi_val '-70' #changed to -70Db
option low_rssi '0'
option rssi_weight '2'
option rssi_center '-60'
option chan_util_val '140'
option chan_util '0'
option max_chan_util_val '170'
option max_chan_util '-10'
option ap_weight '0'
option ht_support '0'
option vht_support '0'
option no_ht_support '0'
option no_vht_support '0'
1 Like
i did replace these 2 section on both APs and rebooted
so go from one AP to the other AP and when i see -71Db -76Db i wait and i see even if it is -75 for 20 seconds it doents kicked or switched till it is -85Db
but somtimes , like 1 of 10 switches i got -65Db ----> -45Db and that is the best of cause,
also i tryed FT over DS and FT over AIR not much diffrence
and here is my log
Mon Feb 14 15:39:20 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:39:30 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:39:33 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -33, freq : 2462
Mon Feb 14 15:39:33 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:39:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:39:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:39:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:39:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:39:33 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -33, freq : 2462
Mon Feb 14 15:39:33 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Mon Feb 14 15:39:33 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:39:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:39:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:39:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Mon Feb 14 15:39:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Mon Feb 14 15:39:40 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:39:40 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:39:40 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:39:50 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:39:50 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:39:50 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 1.000000
Mon Feb 14 15:39:50 2022 daemon.info dawn[1738]: Kicking NR entry: f8:5e:3c:0c:59:10, score=44
Mon Feb 14 15:39:50 2022 daemon.info dawn[1738]: BSS TRANSITION NEIGHBOR f8:5e:3c:0c:59:10, Score=44
Mon Feb 14 15:39:50 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:39:50 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: disassociated due to inactivity
Mon Feb 14 15:39:50 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DISASSOCIATE.indication(0e:46:ff:cd:9f:c0, 2)
Mon Feb 14 15:39:50 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:39:51 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Feb 14 15:39:51 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DEAUTHENTICATE.indication(0e:46:ff:cd:9f:c0, 2)
Mon Feb 14 15:39:51 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:40:00 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:40:10 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:40:13 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -27, freq : 2462
Mon Feb 14 15:40:13 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:40:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:40:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:40:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:40:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:40:13 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -27, freq : 2462
Mon Feb 14 15:40:13 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Mon Feb 14 15:40:13 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:40:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:40:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:40:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Mon Feb 14 15:40:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Mon Feb 14 15:40:20 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:40:20 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:40:20 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:40:30 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:40:30 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:40:30 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:40:33 2022 daemon.info dawn[1738]: MAC not found!
Mon Feb 14 15:40:33 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -53, freq : 2462
Mon Feb 14 15:40:33 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:40:33 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:40:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:40:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:40:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:40:33 2022 daemon.notice hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: did not acknowledge authentication response
Mon Feb 14 15:40:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:40:33 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -89, freq : 2462
Mon Feb 14 15:40:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: did not acknowledge association response
Mon Feb 14 15:40:40 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:40:40 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:40:40 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:40:40 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:40:40 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:40:43 2022 daemon.info dawn[1738]: MAC not found!
Mon Feb 14 15:40:43 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -53, freq : 2462
Mon Feb 14 15:40:43 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:40:43 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:40:43 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:40:43 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:40:43 2022 daemon.notice hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: did not acknowledge authentication response
Mon Feb 14 15:40:43 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:40:43 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -52, freq : 2462
Mon Feb 14 15:40:43 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: did not acknowledge association response
Mon Feb 14 15:40:50 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:40:50 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:40:50 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:40:50 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:40:50 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:40:53 2022 daemon.info dawn[1738]: MAC not found!
Mon Feb 14 15:41:00 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:00 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:00 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:41:00 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:41:00 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:41:03 2022 daemon.info dawn[1738]: MAC not found!
Mon Feb 14 15:41:10 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:10 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:10 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:41:10 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:41:10 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:41:13 2022 daemon.info dawn[1738]: MAC not found!
Mon Feb 14 15:41:13 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -53, freq : 2462
Mon Feb 14 15:41:13 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:41:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:41:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:41:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:41:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:41:13 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -53, freq : 2462
Mon Feb 14 15:41:13 2022 daemon.notice hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: did not acknowledge authentication response
Mon Feb 14 15:41:13 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: did not acknowledge association response
Mon Feb 14 15:41:20 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:20 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:20 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:41:20 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:41:20 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:41:30 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:30 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:30 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:41:30 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:41:30 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:41:33 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -53, freq : 2462
Mon Feb 14 15:41:33 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:41:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:41:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:41:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:41:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:41:33 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -53, freq : 2462
Mon Feb 14 15:41:33 2022 daemon.notice hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: did not acknowledge authentication response
Mon Feb 14 15:41:33 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: did not acknowledge association response
Mon Feb 14 15:41:40 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:40 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:40 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:41:40 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:41:40 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:41:50 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:50 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:41:50 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:41:50 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:41:50 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:42:00 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:42:00 2022 daemon.warn dawn[1738]: No station connected
Mon Feb 14 15:42:00 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:42:00 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:42:00 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:42:03 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -41, freq : 2462
Mon Feb 14 15:42:03 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:42:03 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:42:03 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:42:03 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:42:03 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:42:03 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -40, freq : 2462
Mon Feb 14 15:42:03 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Mon Feb 14 15:42:03 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:42:03 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:42:03 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:42:03 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Mon Feb 14 15:42:03 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Mon Feb 14 15:42:10 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:42:10 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:42:10 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:42:20 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:42:20 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:42:20 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 6.000000
Mon Feb 14 15:42:20 2022 daemon.info dawn[1738]: Kicking NR entry: f8:5e:3c:0c:59:10, score=68
Mon Feb 14 15:42:20 2022 daemon.info dawn[1738]: BSS TRANSITION NEIGHBOR f8:5e:3c:0c:59:10, Score=68
Mon Feb 14 15:42:21 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:42:21 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: disassociated due to inactivity
Mon Feb 14 15:42:21 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DISASSOCIATE.indication(0e:46:ff:cd:9f:c0, 2)
Mon Feb 14 15:42:21 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:42:22 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Feb 14 15:42:22 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DEAUTHENTICATE.indication(0e:46:ff:cd:9f:c0, 2)
Mon Feb 14 15:42:22 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:42:30 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:42:40 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:42:50 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:43:00 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:43:01 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -23, freq : 2462
Mon Feb 14 15:43:01 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:43:01 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:43:01 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:43:01 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:43:01 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:43:01 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -23, freq : 2462
Mon Feb 14 15:43:01 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Mon Feb 14 15:43:01 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:43:01 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:43:01 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:43:01 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Mon Feb 14 15:43:01 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Mon Feb 14 15:43:03 2022 daemon.info dawn[1738]: MAC not found!
Mon Feb 14 15:43:10 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:43:10 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:43:10 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:43:20 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:43:20 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:43:20 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 1.000000
Mon Feb 14 15:43:20 2022 daemon.info dawn[1738]: Kicking NR entry: f8:5e:3c:0c:59:10, score=64
Mon Feb 14 15:43:20 2022 daemon.info dawn[1738]: BSS TRANSITION NEIGHBOR f8:5e:3c:0c:59:10, Score=64
Mon Feb 14 15:43:21 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:43:21 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: disassociated due to inactivity
Mon Feb 14 15:43:21 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DISASSOCIATE.indication(0e:46:ff:cd:9f:c0, 2)
Mon Feb 14 15:43:21 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:43:22 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Feb 14 15:43:22 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DEAUTHENTICATE.indication(0e:46:ff:cd:9f:c0, 2)
Mon Feb 14 15:43:22 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:43:30 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:43:40 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:43:50 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:44:00 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:44:10 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:44:16 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -39, freq : 2462
Mon Feb 14 15:44:16 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:44:16 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:44:16 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:44:16 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:44:16 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:44:16 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -39, freq : 2462
Mon Feb 14 15:44:16 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Mon Feb 14 15:44:16 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:44:16 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:44:16 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:44:16 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Mon Feb 14 15:44:16 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Mon Feb 14 15:44:20 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:44:20 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:44:20 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:44:23 2022 daemon.info dawn[1738]: MAC not found!
Mon Feb 14 15:44:31 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:44:31 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:44:31 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:44:41 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:44:41 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:44:41 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 6.000000
Mon Feb 14 15:44:41 2022 daemon.info dawn[1738]: Kicking NR entry: f8:5e:3c:0c:59:10, score=36
Mon Feb 14 15:44:41 2022 daemon.info dawn[1738]: BSS TRANSITION NEIGHBOR f8:5e:3c:0c:59:10, Score=36
Mon Feb 14 15:44:41 2022 daemon.notice hostapd: wlan0: BSS-TM-RESP 0e:46:ff:cd:9f:c0 status_code=0 bss_termination_delay=0 target_bssid=f8:5e:3c:0c:59:10
Mon Feb 14 15:44:41 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:44:41 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: disassociated due to inactivity
Mon Feb 14 15:44:41 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DISASSOCIATE.indication(0e:46:ff:cd:9f:c0, 2)
Mon Feb 14 15:44:41 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:44:42 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Feb 14 15:44:42 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DEAUTHENTICATE.indication(0e:46:ff:cd:9f:c0, 2)
Mon Feb 14 15:44:42 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:44:51 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:45:01 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:45:11 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:45:15 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -28, freq : 2462
Mon Feb 14 15:45:15 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:45:15 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:45:15 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:45:15 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:45:15 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:45:15 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -26, freq : 2462
Mon Feb 14 15:45:15 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Mon Feb 14 15:45:15 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:45:15 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:45:15 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:45:15 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Mon Feb 14 15:45:15 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Mon Feb 14 15:45:21 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:45:21 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:45:21 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:45:23 2022 daemon.info dawn[1738]: MAC not found!
Mon Feb 14 15:45:31 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:45:31 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:45:31 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:45:41 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:45:41 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:45:41 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:45:51 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:45:51 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:45:51 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:46:01 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:46:01 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:46:01 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Mon Feb 14 15:46:11 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:46:11 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:46:11 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 1.000000
Mon Feb 14 15:46:11 2022 daemon.info dawn[1738]: Kicking NR entry: f8:5e:3c:0c:59:10, score=76
Mon Feb 14 15:46:11 2022 daemon.info dawn[1738]: BSS TRANSITION NEIGHBOR f8:5e:3c:0c:59:10, Score=76
Mon Feb 14 15:46:11 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:46:11 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: disassociated due to inactivity
Mon Feb 14 15:46:11 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DISASSOCIATE.indication(0e:46:ff:cd:9f:c0, 2)
Mon Feb 14 15:46:11 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:46:12 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Feb 14 15:46:12 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DEAUTHENTICATE.indication(0e:46:ff:cd:9f:c0, 2)
Mon Feb 14 15:46:12 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:46:21 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:46:31 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:46:40 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -22, freq : 2462
Mon Feb 14 15:46:40 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Feb 14 15:46:40 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:46:40 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Mon Feb 14 15:46:40 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Mon Feb 14 15:46:40 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Mon Feb 14 15:46:40 2022 daemon.info dawn[1738]: bssid_addr: 68:15:90:E7:59:FC, client_addr: 0E:46:FF:CD:9F:C0, signal : -23, freq : 2462
Mon Feb 14 15:46:40 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Mon Feb 14 15:46:40 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Mon Feb 14 15:46:40 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Mon Feb 14 15:46:40 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Mon Feb 14 15:46:40 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Mon Feb 14 15:46:40 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Mon Feb 14 15:46:41 2022 daemon.info dawn[1738]: AP BSSID 68:15:90:E7:59:FC: Looking for candidates to kick
Mon Feb 14 15:46:41 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Mon Feb 14 15:46:41 2022 daemon.info dawn[1738]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Also there is a bad bug
somtimes when i go from one point to another (-79 and lower) it switches to best one via 802.11r and 2-10 seconds later get disconnected from -45 the best one for 2 second and then connects to the best one again
What are the relevant scores in get_hearing_map at that point? Remember that DAWN doesn't update all of its data in real time. It uses the values in the "times" configuration section for some things for example. So what you see in the main OpenWrt overview screen may not be what DAWN is aware of yet.
Does DAWN actually kick it from the -45dB one? As we said above it is ultimately up to the client device what it connects to. It might think it still wants to be connected to the original, and then decide not.
EDIT: You could try adjusting update_beacon_reports in the times section to 5 (seconds) to see if it helps speed things up.
1 Like