Intermittent disconnections on Zoneflex 7363

  • 1
  • Question
  • Updated 11 months ago
  • Answered
Some users complain of this. The log is

Apr 11 11:18:17 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: disassociated
Apr 11 11:18:18 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: associated
Apr 11 11:18:18 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf WPA: pairwise key handshake completed (RSN)
Apr 11 11:18:21 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: disassociated
Apr 11 11:18:21 RuckusAP_Level_3 daemon.warn Eved: STA-DISASSOC-REASON,nimac=9c:2a:83:5a:8c:bf,func=ieee80211_send_mgmt,line=4492,hint=send station disassociate,rx_rssi=24,ack_rssi=0,reason=2,freq=2462,chan=11,stats=(0,0,0,0)
Apr 11 11:18:21 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: unknown reason code= 2
Apr 11 11:18:22 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: associated
Apr 11 11:18:22 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf WPA: pairwise key handshake completed (RSN)
Apr 11 11:19:10 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124)
Apr 11 11:20:10 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124)
Apr 11 11:21:05 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 00:27:10:47:84:e8 IEEE 802.11: associated
Apr 11 11:21:06 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 00:27:10:47:84:e8 WPA: pairwise key handshake completed (RSN)
Apr 11 11:21:08 RuckusAP_Level_3 user.warn kernel: ath_aggr_delba_process Class 1 tid->tidpause 1 reset tidpause
Apr 11 11:21:13 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124)
Apr 11 11:22:15 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124)
Apr 11 11:23:24 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124)
Apr 11 11:24:30 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124)
Apr 11 11:24:52 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: disassociated
Apr 11 11:24:52 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: unknown reason code= 2
Apr 11 11:24:52 RuckusAP_Level_3 daemon.warn Eved: STA-DISASSOC-REASON,nimac=9c:2a:83:5a:8c:bf,func=ieee80211_send_mgmt,line=4492,hint=send station disassociate,rx_rssi=26,ack_rssi=0,reason=2,freq=2462,chan=11,stats=(0,0,0,0)
Apr 11 11:24:52 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: associated
Apr 11 11:24:52 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf WPA: pairwise key handshake completed (RSN)
Apr 11 11:24:55 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: disassociated
Apr 11 11:24:55 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: unknown reason code= 2
Apr 11 11:24:55 RuckusAP_Level_3 daemon.warn Eved: STA-DISASSOC-REASON,nimac=9c:2a:83:5a:8c:bf,func=ieee80211_send_mgmt,line=4492,hint=send station disassociate,rx_rssi=26,ack_rssi=0,reason=2,freq=2462,chan=11,stats=(0,0,0,0)
Apr 11 11:24:55 RuckusAP_Level_3 daemon.warn Eved: STA-DISASSOC-REASON,nimac=c4:10:8a:18:fb:78,func=ieee80211_recv_mgmt,line=7011,hint=recv disassociate (reason 7),rx_rssi=26,ack_rssi=0,reason=7,freq=2462,chan=11,stats=(0,0,27580670,4867526533)
Apr 11 11:25:35 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124)
Apr 11 11:25:59 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: associated
Apr 11 11:25:59 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf WPA: pairwise key handshake completed (RSN)
Apr 11 11:26:01 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: disassociated
Apr 11 11:26:01 RuckusAP_Level_3 daemon.info hostapd: wlan0: STA 9c:2a:83:5a:8c:bf IEEE 802.11: unknown reason code= 2
Apr 11 11:26:01 RuckusAP_Level_3 daemon.warn Eved: STA-DISASSOC-REASON,nimac=9c:2a:83:5a:8c:bf,func=ieee80211_send_mgmt,line=4492,hint=send station disassociate,rx_rssi=27,ack_rssi=0,reason=2,freq=2462,chan=11,stats=(0,0,0,0)
Apr 11 11:26:02 RuckusAP_Level_3 daemon.warn Eved: STA-DISASSOC-REASON,nimac=c4:10:8a:18:fb:78,func=ieee80211_recv_mgmt,line=7011,hint=recv disassociate (reason 7),rx_rssi=28,ack_rssi=0,reason=7,freq=2462,chan=11,stats=(0,0,27581924,4867756276)
Apr 11 11:26:02 RuckusAP_Level_3 daemon.warn Eved: STA-DISASSOC-REASON,nimac=c4:10:8a:18:fb:78,func=ieee80211_recv_mgmt,line=7011,hint=recv disassociate (reason 7),rx_rssi=28,ack_rssi=0,reason=7,freq=2462,chan=11,stats=(0,0,27581924,4867756276)
Apr 11 11:26:02 RuckusAP_Level_3 daemon.warn Eved: STA-DISASSOC-REASON,nimac=c4:10:8a:18:fb:78,func=ieee80211_recv_mgmt,line=7011,hint=recv disassociate (reason 7),rx_rssi=26,ack_rssi=0,reason=7,freq=2462,chan=11,stats=(0,0,27581924,4867756276)
Apr 11 11:26:02 RuckusAP_Level_3 daemon.warn Eved: STA-DISASSOC-REASON,nimac=c4:10:8a:18:fb:78,func=ieee80211_recv_mgmt,line=7011,hint=recv disassociate (reason 7),rx_rssi=26,ack_rssi=0,reason=7,freq=2462,chan=11,stats=(0,0,27581924,4867756276)
Apr 11 11:26:02 RuckusAP_Level_3 daemon.warn Eved: STA-DISASSOC-REASON,nimac=c4:10:8a:18:fb:78,func=ieee80211_recv_mgmt,line=7011,hint=recv disassociate (reason 7),rx_rssi=27,ack_rssi=0,reason=7,freq=2462,chan=11,stats=(0,0,27581924,4867756276)
Apr 11 11:26:33 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124)
Apr 11 11:27:30 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124)
Apr 11 11:28:31 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124)
  • Apr 11 11:29:29 RuckusAP_Level_3 local2.err syslog: Cannot notify kernel for Delete AP (65535) event, -- Address family not supported by protocol(124) nimac=c0:bd:
Any ideas?
Photo of matt heaven

matt heaven

  • 3 Posts
  • 0 Reply Likes

Posted 11 months ago

  • 1
Photo of Michael Brado

Michael Brado, Official Rep

  • 2114 Posts
  • 297 Reply Likes
Hi Matt,
   First look at 802.11 reason codes, from KBA-4363:  https://support.ruckuswireless.com/answers/000004263
said the first unknown reason code 2 = previous authentication no longer valid (samsung client OUI),
https://www.wireshark.org/tools/oui-lookup.html  and the lower reason code 7 = Class 3 frame received from
non-associated STA (Ruckus OUI, a Mesh AP perhaps?). We really can't interpret too much from this brief log info.
  
Photo of matt heaven

matt heaven

  • 3 Posts
  • 0 Reply Likes
When I click the link it takes me to https://support.ruckuswireless.com/buy_support Surely I don't have to pay to read a KB article?
Photo of Michael Brado

Michael Brado, Official Rep

  • 2076 Posts
  • 289 Reply Likes
Unlike some competitors who won't let you on their website without Support,
Ruckus does require something under support for your privileged accesss
for firmware downloads and Knowledge Base Article visibility.  But the reason
codes are found on the Internet too, and I'll share them here.  You may still
wish/need to communicate with our TS or your local VAR about your specific
environment/client issues.

When an Access Point (AP) disconnects a UE, according to the 802.11 standard, it must provide a reason code for why this event took place.
Below is a table of the reason code numbers and their associated descriptions.
 
Reason Code   
Description0   Reserved
1   Unspecified Reason
2Previous authentication no longer valid
3Deauthenticated because sending STA is leaving (or has left) IBSS or ESS
4Disassociated due to inactivity
5Disassociated because AP is unable to handle all currently associated STAs
6Class 2 frame received from nonauthenticated STA
7Class 3 frame received from nonassociated STA
8Disassociated because sending STA is leaving (or has left) BSS
9STA requesting (re)association is not authenticated with responding STA
10Disassociated because the information in the Power Capability element is unacceptable
11Disassociated because the information in the Supported Channels element is unacceptable
12Reserved
13Invalid information element, i.e., an information element defined in this standard for which the content does not meet the specifications
14Message integrity code (MIC) failure
154-Way Handshake timeout
16Group Key Handshake timeout
17Information element in 4-Way Handshake different from (Re)Association Request/Probe Response/Beacon frame
18Invalid group cipher
19Invalid pairwise cipher
20Invalid AKMP
21Unsupported RSN information element version
22Invalid RSN information element capabilities
23IEEE 802.1X authentication failed
24Cipher suite rejected because of the security policy
25-31Reserved
32Disassociated for unspecified, QoS-related reason
33Disassociated because QoS AP lacks sufficient bandwidth for this QoS STA
34Disassociated because excessive number of frames need to be acknowledged, but are not acknowledged due to AP transmissions and/or poor channel conditions
35Disassociated because STA is transmitting outside the limits of its TXOPs
35Requested from peer STA as the STA is leaving the BSS (or resetting)
37Requested from peer STA as it does not want to use the mechanism
38Requested from peer STA as the STA received frames using the mechanism for which a setup is required
39Requested from peer STA due to timeout45Peer STA does not support the requested cipher suite46–65Reserved
Photo of matt heaven

matt heaven

  • 3 Posts
  • 0 Reply Likes
Thanks for that. To pinpoint problems I need the log date and time correct. But the log dates and times are way out. The time server is set to ntp.ruckuswireless.com but the access point time is

Current Time (GMT):     Wed Apr 8 19:15:28 2015

Do you know how I can fix this?
(Edited)