802.11r/k DAWN /etc/config/dawn

The problem is the same for 802.11r - the devices stick to one AP and roam only when signal level is too bad like -80db

I have installed OpenWRT 21.0.2 wpad and dawn my routers are ZBT 8005 2.4Ghz only
in luci interface there is nothing but information no settings but in
/etc/config/dawn there are settings but i cant find any information how to configure it
so here is the config

config network
    option broadcast_ip         '192.168.222.255'   // as i understand i shood put my network here? mine is 192.168.222.0/24
    option broadcast_port       '1025'
    option server_ip            ''    // what server ?
    option tcp_port             '1026'
    option network_option       '2' # 0 udp broadcast, 1 multicast, 2 tcp
    option shared_key           'Niiiiiiiiiiiiick' // what is this key ?
    option iv                   'Niiiiiiiiiiiiick'
    option use_symm_enc         '0'
    option collision_domain     '-1'     # enter here aps which are in the same collision domain //what shood i put IP adress? or what 
    option bandwidth            '-1'     # enter network bandwidth  // 2.4G ?

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          '0'
    option rssi_center          '0'
    option initial_score        '0'
    option kicking_threshold    '20'
    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         '-75'
    option chan_util_val        '0'
    option max_chan_util_val    '0'
    option min_probe_count      '0'
    option bandwidth_threshold  '6'
    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              '0'
    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'

config metric 802_11a
    option rssi_weight          '2'
    option rssi_center          '-65'
    option initial_score        '125'

config metric 802_11g
    option rssi_weight          '2'
    option rssi_center          '-65'
    option initial_score        '100'

Should i have only one DAWN in my WIFI domain or on each APs?

in luci i have only these: no options just info



and here is my wireless config

config wifi-device 'radio0'
	option type 'mac80211'
	option hwmode '11g'
	option path 'platform/10180000.wmac'
	option htmode 'HT20'
	option cell_density '0'
	option channel '6'
	option log_level '1'
	option bss_transition '1'
	option txpower '3'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'Open22Wrt'
	option encryption 'psk2'
	option key '1225612256'
	option ieee80211r '1'
	option mobility_domain '5555'
	option r0_key_lifetime '10000'
	option reassociation_deadline '1000'
	option pmk_r1_push '1'
	option nasid 'F85E3C0C5910'
	option ft_psk_generate_local '0'
	option r1_key_holder 'F85E3C0C5910'
	option ieee80211k '1'
	option ft_over_ds '0'
	list r0kh '68:15:90:E7:59:FC,681590E759FC,8a7fcc966ed0691ff2809e1f38c16996'
	list r0kh 'F8:5E:3C:0C:59:10,F85E3C0C5910,8a7fcc966ed0691ff2809e1f38c16996'
	list r1kh '68:15:90:E7:59:FC,68:15:90:E7:59:FC,8a7fcc966ed0691ff2809e1f38c16996'
	list r1kh 'F8:5E:3C:0C:59:10,F8:5E:3C:0C:59:10,8a7fcc966ed0691ff2809e1f38c16996'

and hostapd

driver=nl80211
logger_syslog=127
logger_syslog_level=1
logger_stdout=127
logger_stdout_level=1
hw_mode=g
supported_rates=60 90 120 180 240 360 480 540
basic_rates=60 120 240
beacon_int=100
dtim_period=2
channel=6
chanlist=6


ieee80211n=1
ht_coex=0
ht_capab=[SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC12]

radio_config_id=0b06d61b1f48056d813099732f079b9c
interface=wlan0
ctrl_interface=/var/run/hostapd
ap_isolate=1
bss_load_update_period=60
chan_util_avg_period=600
disassoc_low_ack=1
skip_inactivity_poll=0
preamble=1
wmm_enabled=1
ignore_broadcast_ssid=0
uapsd_advertisement_enabled=1
utf8_ssid=1
multi_ap=0
nas_identifier=F85E3C0C5910
wpa_passphrase=1225612256
wpa_psk_file=/var/run/hostapd-wlan0.psk
auth_algs=1
wpa=2
wpa_pairwise=CCMP
ssid=Open22Wrt
bridge=br-lan
rrm_neighbor_report=1
rrm_beacon_report=1
mobility_domain=5555
ft_psk_generate_local=0
ft_over_ds=0
reassociation_deadline=1000
r1_key_holder=F85E3C0C5910
r0_key_lifetime=10000
pmk_r1_push=1
r0kh=68:15:90:E7:59:FC 681590E759FC 8a7fcc966ed0691ff2809e1f38c16996
r0kh=F8:5E:3C:0C:59:10 F85E3C0C5910 8a7fcc966ed0691ff2809e1f38c16996
r1kh=68:15:90:E7:59:FC 68:15:90:E7:59:FC 8a7fcc966ed0691ff2809e1f38c16996
r1kh=F8:5E:3C:0C:59:10 F8:5E:3C:0C:59:10 8a7fcc966ed0691ff2809e1f38c16996
wpa_disable_eapol_key_retries=0
wpa_key_mgmt=WPA-PSK FT-PSK
okc=0
disable_pmksa_caching=1
dynamic_vlan=0
vlan_naming=1
vlan_file=/var/run/hostapd-wlan0.vlan
config_id=317235459cc5cd0a4c83d1ee1112a890
bssid=f8:5e:3c:0c:59:10

any advise ?

This is possibly the reason

I guess there is two ways a clients roam:

  1. Client initiative
  2. AP initiative

For 1) tune the transmit powers such that the transition occurs halfway between APs (see 802.11r/k DAWN /etc/config/dawn)
For 2) the AP needs to send the disconnect imminent message. Then give the client time to roam, if they dont the AP could disconnect them but then the client may loose connection altogether...

So the point is, if a client is behaving badly, you cant fix it...

1 Like

The question is what should I put in the

config network
    option broadcast_ip         '192.168.222.255'   // as i understand i shood put my network here? mine is 192.168.222.0/24
    option broadcast_port       '1025'
    option server_ip            ''    // what server ?
    option tcp_port             '1026'
    option network_option       '2' # 0 udp broadcast, 1 multicast, 2 tcp
    option shared_key           'Niiiiiiiiiiiiick' // what is this key ?
    option iv                   'Niiiiiiiiiiiiick'
    option use_symm_enc         '0'
    option collision_domain     '-1'     # enter here aps which are in the same collision domain //what shood i put IP adress? or what 
    option bandwidth            '-1'     # enter network bandwidth  // 2.4G ?

At first glance, the "kicking" option is 0, meaning disabled - if this is the default then I'm not sure why as it will disappoint a lot of people :expressionless: . Try setting it to 1.

EDIT: And I'm hoping to add some updated config / developer info before making a PR from my latest updates to DAWN.

2 Likes

I am more worryed of config network section like shoud i change somthing there or not
all i did i changed option broadcast_ip , but there are many other options like
option server_ip
option shared_key
option shared_key
option bandwidth

we really need some documentation and explanation :neutral_face:

1 Like

I'm writing it this morning. It'll be in my next commit. I didn't write the networking code originally, so am reverse engineering things and may have it bit incorrect though :open_mouth:.

Networking Parameters

TCP networking with UMDNS and without encryption is the most tested and stable configuration.

Encryption has been reported to be broken, so use it with caution.

Other parameters have fallen out of use, but remain in the code. A tidy up of them is due.

These parameters go in the following section:

config network
Parameter Purpose Notes [Default is bracketed]
bandwidth Unused N/A
broadcast_ip IP address for broadcast and multicast No default
broadcast_port IP port for broadcast and multicast [1026]
collision_domain Unused N/A
iv Unused N/A
network_option Method of networking between DAWN instances 0 = Broadcast; 2 = Multicast; [2 = TCP with UMDNS discovery]; 3 = TCP w/out UMDNS discovery
server_ip IP address when not using UMDNS No default
shared_key Unused N/A
tcp_port Port for TCP networking [1025]
use_symm_enc Enable encryption of network traffic [0 = Disabled]; 1 = Enabled
1 Like

I disabled rrm_nr scripts on both APs and enebled DAWN then reboot both APs
option log_level=1 in configwif device .
aslo i changed dawn config like this

config network
    option broadcast_ip         ''
    option broadcast_port       '1025'
    option server_ip            ''
    option tcp_port             '1026'
    option network_option       '2' # 0 udp broadcast, 1 multicast, 2 tcp
    option shared_key           'Niiiiiiiiiiiiick'
    option iv                   'Niiiiiiiiiiiiick'
    option use_symm_enc         '0'
    option collision_domain     '-1'     # enter here aps which are in the same collision domain
    option bandwidth            '-1'     # enter network bandwidth

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          '0'
    option rssi_center          '0'
    option initial_score        '0'
    option kicking_threshold    '20'
    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             '-69'
    option low_rssi_val         '-70'
    option chan_util_val        '0'
    option max_chan_util_val    '0'
    option min_probe_count      '0'
    option bandwidth_threshold  '6'
    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       '2'



config metric 802_11g
    option rssi_weight          '2'
    option rssi_center          '-60'
    option initial_score        '100'

and in syslog i got this

Sun Feb  6 16:11:30 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:11:30 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Sun Feb  6 16:11:30 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Sun Feb  6 16:11:30 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Sun Feb  6 16:11:30 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Sun Feb  6 16:11:30 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:11:30 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:11:30 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:11:30 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Sun Feb  6 16:11:30 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Sun Feb  6 16:15:22 2022 daemon.notice hostapd: wlan0: BEACON-REQ-TX-STATUS 0e:46:ff:cd:9f:c0 1 ack=1
Sun Feb  6 16:15:22 2022 daemon.notice hostapd: wlan0: BEACON-RESP-RX 0e:46:ff:cd:9f:c0 1 00 5106f4e95223000000000300045afff85e3c0c59100170f95223
Sun Feb  6 16:16:09 2022 authpriv.info dropbear[2299]: Child connection from 192.168.222.55:62966
Sun Feb  6 16:16:10 2022 authpriv.notice dropbear[2299]: Auth succeeded with blank password for 'root' from 192.168.222.55:62966
Sun Feb  6 16:16:29 2022 daemon.err dawn[1543]: client_to_server_state()=tcpsocket.c@98 eof!, pending: 0, total: 33816578
Sun Feb  6 16:16:29 2022 daemon.warn dawn[1543]: Connection to server closed
Sun Feb  6 16:16:29 2022 daemon.err dawn[1543]: client_notify_state()=tcpsocket.c@68 eof!, pending: 0, total: 0
Sun Feb  6 16:16:29 2022 daemon.warn dawn[1543]: Connection closed
Sun Feb  6 16:16:43 2022 daemon.warn dawn[2343]: Failed to update rssi!
Sun Feb  6 16:16:43 2022 daemon.warn dawn[2343]: Current AP not found in probe array!
Sun Feb  6 16:16:43 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:16:43 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DEAUTHENTICATE.indication(0e:46:ff:cd:9f:c0, 0)
Sun Feb  6 16:16:43 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:16:43 2022 daemon.notice hostapd: Beacon request: 0e:46:ff:cd:9f:c0 is not connected
Sun Feb  6 16:16:48 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: deauthenticated due to local deauth request
Sun Feb  6 16:16:53 2022 daemon.warn dawn[2343]: No station connected
Sun Feb  6 16:16:53 2022 daemon.warn dawn[2343]: No station connected
Sun Feb  6 16:16:53 2022 daemon.warn dawn[2343]: Current AP not found in probe array!
Sun Feb  6 16:16:59 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sun Feb  6 16:16:59 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:16:59 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Sun Feb  6 16:16:59 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Sun Feb  6 16:16:59 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Sun Feb  6 16:16:59 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Sun Feb  6 16:16:59 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:16:59 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:16:59 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:16:59 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Sun Feb  6 16:16:59 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Sun Feb  6 16:17:23 2022 daemon.info dawn[2343]: Station 0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 1.000000
Sun Feb  6 16:17:24 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:17:24 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: disassociated due to inactivity
Sun Feb  6 16:17:24 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DISASSOCIATE.indication(0e:46:ff:cd:9f:c0, 2)
Sun Feb  6 16:17:24 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:17:25 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Feb  6 16:17:25 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DEAUTHENTICATE.indication(0e:46:ff:cd:9f:c0, 2)
Sun Feb  6 16:17:25 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:17:31 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sun Feb  6 16:17:31 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:17:31 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Sun Feb  6 16:17:31 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Sun Feb  6 16:17:31 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Sun Feb  6 16:17:31 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Sun Feb  6 16:17:31 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:17:31 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:17:31 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:17:31 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Sun Feb  6 16:17:31 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Sun Feb  6 16:18:19 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:18:19 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sun Feb  6 16:18:19 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:18:19 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Sun Feb  6 16:18:19 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Sun Feb  6 16:18:19 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Sun Feb  6 16:18:19 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Sun Feb  6 16:18:19 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:18:19 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:18:19 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:18:19 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Sun Feb  6 16:18:19 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Sun Feb  6 16:18:33 2022 daemon.info dawn[2343]: Station 0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 6.000000
Sun Feb  6 16:18:34 2022 daemon.notice hostapd: wlan0: BSS-TM-RESP 0e:46:ff:cd:9f:c0 status_code=0 bss_termination_delay=0 target_bssid=68:15:90:e7:59:fc
Sun Feb  6 16:18:34 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:18:34 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: disassociated due to inactivity
Sun Feb  6 16:18:34 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DISASSOCIATE.indication(0e:46:ff:cd:9f:c0, 2)
Sun Feb  6 16:18:34 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:18:35 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Feb  6 16:18:35 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DEAUTHENTICATE.indication(0e:46:ff:cd:9f:c0, 2)
Sun Feb  6 16:18:35 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:20:51 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sun Feb  6 16:20:51 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:20:51 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Sun Feb  6 16:20:51 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Sun Feb  6 16:20:51 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Sun Feb  6 16:20:51 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Sun Feb  6 16:20:51 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:20:51 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:20:51 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:20:51 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Sun Feb  6 16:20:51 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Sun Feb  6 16:21:32 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:21:32 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sun Feb  6 16:21:32 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:21:32 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Sun Feb  6 16:21:32 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Sun Feb  6 16:21:32 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Sun Feb  6 16:21:32 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Sun Feb  6 16:21:32 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:21:32 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Sun Feb  6 16:21:32 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 16:21:32 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Sun Feb  6 16:21:32 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake

0e:46:ff:cd:9f:c0 is the phone that moves beetwin APs
these massegas doesnt look right
when i
/etc/init.d/dawn disable
/etc/init.d/rrm_nr enable
reboot
there is no messages about BEACON at all in syslog , only about neghbor AP

Sun Feb  6 16:43:42 2022 daemon.info rrm_nr: wlan0: Updating neighbor list (number of neighbors: 1): [[ "68:15:90:e7:59:fc", "Open22Wrt", "681590e759fcaf000000510b060603000000" ]]

I'm not sure if you're saying the kick didn't see to work. I'm assuming that's what you meant, and if not some of the following is unnecessary :slight_smile: .

Most of those messages are hostapd, and I haven't looked at mine enough to know whether this is normal:

Sun Feb 6 16:16:59 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed

Looking at just the DAWN messages when there are two consecutive attempts to kick a client, like this:

Sun Feb  6 16:17:23 2022 daemon.info dawn[2343]: Station 0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 1.000000
Sun Feb  6 16:18:33 2022 daemon.info dawn[2343]: Station 0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 6.000000

It can mean that a "fully featured" wpad-* instance isn't active, and the test for that is that is looking for the wnm_disassoc_imminent method in hostapd:

root@WNDR3700v4:/etc# ubus -v list hostapd.wlan0
'hostapd.wlan0' @9d77e3c6
...
        "wnm_disassoc_imminent":{"addr":"String","duration":"Integer","neighbors":"Array","abridged":"Boolean"}
...

But i think you do have a suitable version. When DAWN tries to kick we see:

Sun Feb  6 16:17:23 2022 daemon.info dawn[2343]: Station 0E:46:FF:CD:9F:C0: Kicking as probably NOT in active transmisison. RxRate is: 1.000000
Sun Feb  6 16:17:24 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 16:17:24 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: disassociated due to inactivity
Sun Feb  6 16:17:25 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Feb  6 16:17:31 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sun Feb  6 16:17:31 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Sun Feb  6 16:17:31 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0

So hostapd does disconnect the client, and then it comes back.

It may be worth looking at the AP you expected it to connect to and see if it was rejected there. And remember it is in the end the choice of a client device where it wants to connect to. 802.11k/v is only a suggestion. DAWN's eval_... parameters can try to enforce it, but I'm not sure that is a good thing to try at the moment - there may be some wrinkles in the behaviour.

1 Like

i just did this caommand and got

root@33:~# ubus -v list hostapd.wlan0
'hostapd.wlan0' @c9a5ca08
        "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"}
root@33:~#

How to activate all the instance ?
i have installed DAWN 2022-01-17-7a726740-1 on 21.02.1 OpenWRT
and if kicking works how to make it kick earlier ? like when it is -75 on the phone

That looks OK.

Your previous message suggested the kick had worked, but you should check what happens on another AP to be sure it "arrives" there.

Kicking is mainly based on RSSI, unless you adjust the HT type parameters to high values. You can make kicking more aggresive by altering the rssi_weight value and kicking_threshold. I think you have them set reasonably at the moment. A 10dB difference at 2 points each hits your threshold of 20. If you make it too "wobbly" then walking past a wall might make it jump from AP1 to AP2 and back again. That may be OK if you have 802.11r working, but is still making the AP work harder than necessary.

EDIT: DAWN has a bit of protection for the walking past a wall scenario. The min_number_to_kick value (which I can't see in your config so should default to 3) is how many consecutive times an AP must be scored as ready to kick before it actually happens. If you set loglevel to 1 then you'd see messages about that.

1 Like

My loglevel in wireless is always 1
kicking more aggresive by altering rssi_weight
i dont understand this value is it in Db? what should i put there ?
i tried to find expanation for every paramets in down config but no lack
can i add min_number_to_kick in my dawn config ?

My understanding is...

Although the 802.11 spec is a bit vague on it the assumption is that each chipset reports RSSI in a linear way. and that each manufacturer uses a scheme where whatever they report in 802.11 messages chnages by 1 for every 1dB of signal strength The actual value can reportedly differ between manufacturers: https://www.metageek.com/training/resources/understanding-rssi/.

The additional "help" is that the figures compared are from the same source: the client device, so whether it uses the 0-60 range or 0-100 range reported in that article at least the figures are comparable when using the weighted points.

So consider two values of 63 and 75. They differ by 12. We use a weight of 2, meaning it is a 24 point difference in score. That exceeds the threshold of 20, so would trigger a kick.

1 Like

I think that's for hostapd. I mean this in /etc/config/dawn (it's a recent option - documentation is coming...):

config local
        option loglevel '1'

Yes, in the 'global' section. Same advice as before though about not making it too trigger happy.

1 Like

will your updates also be backported to 21.02? Would be very nice. :innocent: :sweat_smile: :pray:

2 Likes

Thank a lot for all the answers i find out more for this evening than for 2 weaks serching in internet !

Now i have this in my log

Sun Feb  6 17:51:32 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Sun Feb  6 17:51:42 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:51:42 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:51:42 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Sun Feb  6 17:51:51 2022 daemon.notice hostapd: wlan0: BEACON-REQ-TX-STATUS 0e:46:ff:cd:9f:c0 8 ack=1
Sun Feb  6 17:51:51 2022 daemon.notice hostapd: wlan0: BEACON-RESP-RX 0e:46:ff:cd:9f:c0 8 00 51063a2824d30000000002000440fff85e3c0c591001a43124d3
Sun Feb  6 17:51:52 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:51:52 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:51:52 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Sun Feb  6 17:52:02 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:52:02 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:52:02 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: kickcount 1 below threshold of 2!
Sun Feb  6 17:52:09 2022 daemon.info dawn[2396]: bssid_addr: F8:5E:3C:0C:59:10, client_addr: 0E:46:FF:CD:9F:C0, signal : -92, freq : 2437
Sun Feb  6 17:52:09 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (open system)
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 0 notification
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, OPEN_SYSTEM)
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Sun Feb  6 17:52:09 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authenticated
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Sun Feb  6 17:52:09 2022 daemon.info dawn[2396]: bssid_addr: F8:5E:3C:0C:59:10, client_addr: 0E:46:FF:CD:9F:C0, signal : -94, freq : 2437
Sun Feb  6 17:52:09 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-ASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-DELETEKEYS.request(0e:46:ff:cd:9f:c0)
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 1 notification
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: start authentication
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.1X: unauthorizing port
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: sending 1/4 msg of 4-Way Handshake
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: received EAPOL-Key frame (2/4 Pairwise)
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: sending 3/4 msg of 4-Way Handshake
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: received EAPOL-Key frame (4/4 Pairwise)
Sun Feb  6 17:52:09 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 17:52:09 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.1X: authorizing port
Sun Feb  6 17:52:09 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 RADIUS: starting accounting session 112C24849A264EBD
Sun Feb  6 17:52:09 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: pairwise key handshake completed (RSN)
Sun Feb  6 17:52:12 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:52:12 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:52:12 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Client is probably in active transmisison. Don't kick! RxRate is: 19.500000
Sun Feb  6 17:52:22 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:52:22 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:52:22 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Client is probably in active transmisison. Don't kick! RxRate is: 19.500000
Sun Feb  6 17:52:32 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:52:32 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:52:32 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Client is probably in active transmisison. Don't kick! RxRate is: 13.000000
Sun Feb  6 17:52:42 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:52:42 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:52:42 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Client is probably in active transmisison. Don't kick! RxRate is: 13.000000
Sun Feb  6 17:52:49 2022 daemon.info dawn[2396]: bssid_addr: F8:5E:3C:0C:59:10, client_addr: 0E:46:FF:CD:9F:C0, signal : -70, freq : 2437
Sun Feb  6 17:52:49 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 17:52:49 2022 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sun Feb  6 17:52:49 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 17:52:49 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: authentication OK (FT)
Sun Feb  6 17:52:49 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-AUTHENTICATE.indication(0e:46:ff:cd:9f:c0, FT)
Sun Feb  6 17:52:49 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: association OK (aid 1)
Sun Feb  6 17:52:50 2022 daemon.info dawn[2396]: bssid_addr: F8:5E:3C:0C:59:10, client_addr: 0E:46:FF:CD:9F:C0, signal : -72, freq : 2437
Sun Feb  6 17:52:50 2022 daemon.info hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: associated (aid 1)
Sun Feb  6 17:52:50 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 0e:46:ff:cd:9f:c0
Sun Feb  6 17:52:50 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 MLME: MLME-REASSOCIATE.indication(0e:46:ff:cd:9f:c0)
Sun Feb  6 17:52:50 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 IEEE 802.11: binding station to interface 'wlan0'
Sun Feb  6 17:52:50 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: event 6 notification
Sun Feb  6 17:52:50 2022 daemon.debug hostapd: wlan0: STA 0e:46:ff:cd:9f:c0 WPA: FT authentication already completed - do not start 4-way handshake
Sun Feb  6 17:52:52 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:52:52 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:52:52 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Client is probably in active transmisison. Don't kick! RxRate is: 58.500000
Sun Feb  6 17:53:02 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:53:02 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:53:02 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Current AP is best. Client will stay:
Sun Feb  6 17:53:12 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:53:12 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:53:12 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: kickcount 1 below threshold of 2!
Sun Feb  6 17:53:22 2022 daemon.info dawn[2396]: AP BSSID F8:5E:3C:0C:59:10: Looking for candidates to kick
Sun Feb  6 17:53:22 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Compared 1 alternate AP candidates
Sun Feb  6 17:53:22 2022 daemon.info dawn[2396]: Station 0E:46:FF:CD:9F:C0: Client is probably in active transmisison. Don't kick! RxRate is: 19.500000

seems working the only thing we need now is a good manual or luci dawn settings page
also i it looks like when my phone kicked it tries to get back on the AP wich it has been kicked from

1 Like

That'll be for @PolynomialDivision to look after. I agree it would be good to do so otherwise we'll have confused reports of what is seen on the stable branch. But some testing should be done on SNAPSHOT first I think.

Famous last words, but I hope to make the commit public later today. Just like every day for the last few days - I keep finding new bits that need a tweak :wink:.

That is the challenge of 802.11v - it can be ignored.

2 Likes

how to disable 802.11v i didnt enabled in anywhere but my APs keep advirtasing FT+PSK K V
i also delited section for 5Ghz wifi in dawn config
... so @PolynomialDivision is the guy who makes DAWN ?

They are 802.11r - Fast Transition, etc. There are options in LUCI to disable it IIRC.

Why would you want to disable them? They are probably the most important thing for seamless handover of things like video streaming. In fact, if streaming DAWN should not do the kick due to its "active connection" check. You are then relying on whatever your phone wants to do for moving between APs.

Yes, @PolynomialDivision is the original author of DAWN - I just meddle to make it work a bit better for me and am happy to share the results.

1 Like

i dont have on my routers 2 bands i have only 2.4Ghz why would i neeed this prrotocol if there no second band so no where to stear