topic Re: Many STA-DISASSOC-REASON with reason=1 and ack_rssi=0 in Access Points - Indoor and Outdoor

Many STA-DISASSOC-REASON with reason=1 and ack_rssi=0

jason_reich — Tue, 03 Nov 2020 04:45:55 GMT

In our network of ZF7782 APs (mostly), we're seeing many log STA-DISASSOC-REASON with stable clients. Most of our users are locked to specific APs and using Ubiquiti CPE devices, but we're seeing many disassociations. For example in the support log I'm looking at now, I'm seeing about 150 in a 2 hour period on a single AP with 35 users. Many DISASSOC appear to be after Channelfly changes, but not always. Most of the STA-DISASSOC-REASON messages include "hint=send station disassociate", reason=1, and ack_rssi=0. Example below:

Nov  3 03:31:32 NE FB daemon.warn Eved: STA-DISASSOC-REASON,nimac=80:2a:a8:7c:ea:9a,func=ieee80211_send_mgmt,line=4543,hint=send station disassociate,rx_rssi=44,ack_rssi=0,reason=1,freq=5765,chan=153,stats=(4202,585895,6341,7584346)

The MAC address in the line above is a user we're investigating, as they are seeing disconnect regularly (10-20 times a day), and then reconnect about a minute later. Once they've reconnected, their RSSI values look good again, including values like ack_rssi 45 rx_rssi 45.

What does the "send station disassociate" mean; that the AP is initiating it? If it was the AP, do the other logs below explain why? I know that reason 1 is "unspecified", so that doesn't help me.

What about the ack_rssi=0, what does that mean?

Is it typical to have some some disassoc after a channel switch? Should we disable channel fly?

Any other suggestions of what is going on here, and how to avoid these clients dropping so often?

thanks in advance,

Jason.

PS: having troubles posting a longer log snippet; I'll try in a response.

Re: Many STA-DISASSOC-REASON with reason=1 and ack_rssi=0

jason_reich — Tue, 03 Nov 2020 04:48:10 GMT

(log snippet 1/2)
Nov  3 03:30:48 NE FB user.warn kernel: ath_get_radio_stats:Add counters, tx_errors=46059 rx_errors=455 tx_dropped=0 rx_dropped=0
Nov  3 03:30:48 NE FB user.warn kernel: ath_get_radio_stats:Add counters, tx_errors=9302 rx_errors=4732 tx_dropped=0 rx_dropped=1
Nov  3 03:30:53 NE FB daemon.info channel-wifi1: channelfly detects interference on radio 11a/n and switches from channel 44 to channel 153
Nov  3 03:30:55 NE FB daemon.notice meshd[1960]: IWEVCUSTOM.: CHANNEL-CHANGE.indication: Channel (153)
Nov  3 03:30:55 NE FB daemon.notice meshd[1960]: CHANNEL-CHANGE: Now new channel is 153
Nov  3 03:30:55 NE FB daemon.warn Eved: wifi1: CHANNEL-CHANGE.indication: Channel (153)
Nov  3 03:30:58 NE FB daemon.info channel-wifi1: channelfly stats radio 11a/n chan(44/153) client(24/24) MTBC(100/44)
Nov  3 03:30:58 NE FB user.info kernel: net80211_tac_cfg_sta_set_param(): set station 3c:6a:a7:63:dc:d3 vlan_id = 1
Nov  3 03:30:58 NE FB daemon.info avpd[2281]: avpd_main_loop: 291: receive the ipc message, let's process  
Nov  3 03:30:58 NE FB daemon.info avpd[2281]: avpd_process_cmd_roam_notify: 209: process the CMD_ROAM_NOTIFY_REQ  
Nov  3 03:30:58 NE FB daemon.info avpd[2281]: avpd_process_roam_from: 655:  ==============begin to process roaming from================ 
Nov  3 03:30:58 NE FB daemon.info avpd[2281]: avpd_process_roam_from: 658: station mac:3C:6A:A7:63:DC:D3  
Nov  3 03:30:58 NE FB daemon.info avpd[2281]: avpd_process_roam_from: 664: AP mac (roam from):E0:10:7F:15:8C:80  
Nov  3 03:30:58 NE FB daemon.info avpd[2281]: avpd_process_roam_from: 666: AP IP family (roam from): IPv4 
Nov  3 03:30:58 NE FB daemon.info avpd[2281]: avpd_process_roam_from: 669: AP IPv4 (roam from): 10.1.0.15 
Nov  3 03:30:58 NE FB daemon.info avpd[2281]: avpd_process_roam_from: 680: AP mac (roam to):E0:10:7F:15:8C:80  
Nov  3 03:30:58 NE FB daemon.info avpd[2281]: avpd_process_roam_from: 682: AP IP family (roam to): IPv4

Re: Many STA-DISASSOC-REASON with reason=1 and ack_rssi=0

jason_reich — Tue, 03 Nov 2020 04:53:31 GMT

Sorry, having a tough time adding log messages, not sure if the forum update has made the message limits very small. Here are four disassoc that happen after the above messages.

Nov  3 03:30:58 NE FB daemon.warn Eved: STA-DISASSOC-REASON,nimac=3c:6a:a7:63:dc:d3,func=ieee80211_send_mgmt,line=4543,hint=send station disassociate,rx_rssi=16,ack_rssi=0,reason=1,freq=5765,chan=153,stats=(677,109773,386,132437)
Nov  3 03:31:32 NE FB daemon.warn Eved: STA-DISASSOC-REASON,nimac=80:2a:a8:7c:ea:9a,func=ieee80211_send_mgmt,line=4543,hint=send station disassociate,rx_rssi=44,ack_rssi=0,reason=1,freq=5765,chan=153,stats=(4202,585895,6341,7584346)
Nov  3 03:31:32 NE FB daemon.warn Eved: STA-DISASSOC-REASON,nimac=c4:1c:ff:d0:5e:15,func=ieee80211_send_mgmt,line=4543,hint=send station disassociate,rx_rssi=12,ack_rssi=0,reason=1,freq=2457,chan=10,stats=(1,131,11,1535)
Nov  3 03:31:33 NE FB daemon.warn Eved: STA-DISASSOC-REASON,nimac=80:2a:a8:ba:5a:a7,func=ieee80211_send_mgmt,line=4543,hint=send station disassociate,rx_rssi=44,ack_rssi=0,reason=1,freq=5765,chan=153,stats=(2002972,218171427,3220450,4247202712)

Re: Many STA-DISASSOC-REASON with reason=1 and ack_rssi=0

Zzq — Wed, 10 Jul 2024 03:59:21 GMT

Hi bro, Have you resolved this issue ?