Client "Kicking off STA" "ieee80211_move_to_non_assoc_list,4598" Reason=0

  • 1
  • Question
  • Updated 4 weeks ago
  • (Edited)
Client MAC: ***************
Every hour or so a number statically assigned clients running our POS software will randomly lose internet connectivity and not roam. The AP's are managed through a ZoneDirector 3000 on firmware 9.9.1.0 build 31

Below is a log showing this with the Reason=0, I can't find anything about this error reason, nor any reason as to why they would be getting kicked to the non associated list. 

Is there a way to prevent this and always associate per IP address or Mac? This is most common when the client should be roaming but it never does, it sticks to the further away AP and never roams. Usually rebooting the AP's resolves this but we need a better way to resolve it without taking down the POS wifi.


Nov 19 19:18:16 Plaza Queue daemon.info hostapd: wlan35: STA *************** IEEE 802.11: associated
Nov 19 19:18:16 Plaza Queue user.warn kernel: wmi_unified_vdev_install_key_send Setting Key for Macaddress: 
Nov 19 19:18:16 Plaza Queue user.warn kernel: Keyix=0 Keylen=16 Keyflags=0 Cipher=4 
Nov 19 19:18:16 Plaza Queue user.warn kernel:  Keydata= 
Nov 19 19:18:16 Plaza Queue daemon.info hostapd: wlan35: STA *************** WPA: pairwise key handshake completed (RSN)
Nov 19 19:58:56 Plaza Queue user.warn kernel: FWLOG: [119009241] WAL_DBGID_STA_VDEV_XRETRY ( 0x40 )
Nov 19 19:58:56 Plaza Queue daemon.info hostapd: wlan35: STA *************** IEEE 802.11: disassociated
Nov 19 19:58:56 Plaza Queue daemon.warn Eved: STA-DISASSOC-REASON,nimac=***************,func=wmi_peer_sta_kickout_event_handler,line=841,hint= STA kicked-out ,rx_rssi=8,ack_rssi=0,reason=0,freq=5765,chan=153,stats=(27214,2827229,30080,4690190)
Nov 19 19:58:56 Plaza Queue user.warn kernel: wmi_peer_sta_kickout_event_handler:838 Kicking off STA *************** AID 3
Nov 19 19:58:56 Plaza Queue user.warn kernel: ieee80211_move_to_non_assoc_list,4598: Calling ol_node_peerdelete ***************...
Nov 19 19:58:57 Plaza Queue user.warn kernel: FWLOG: [119010194] WAL_DBGID_STA_KICKOUT ( 0x200 )
Nov 19 19:59:02 Plaza Queue local2.err syslog: lwapp_send_pkt(6170), sends packet out with length: 1041 

Photo of Prime Shine Car Wash

Prime Shine Car Wash

  • 2 Posts
  • 0 Reply Likes

Posted 4 weeks ago

  • 1
Photo of Andrea Coppini

Andrea Coppini

  • 66 Posts
  • 29 Reply Likes
Signal too low (RX_RSSI=8).  Have you enabled SmartRoam by any chance? Default is off, you would know if you did.  If not, it sounds like the path loss is simply too large (ie. signal from client to AP is too low) so the AP thinks the client simply disappeared.  Try adding an AP closer to the client.
Photo of Prime Shine Car Wash

Prime Shine Car Wash

  • 2 Posts
  • 0 Reply Likes
SmartRoam is disabled. Usually this happens where the client is closer to another AP and should be roaming but it stays stuck to the first one. As in you can take the device and stand under the neighboring AP and it won't roam to it.
Photo of Andrea Coppini

Andrea Coppini

  • 66 Posts
  • 29 Reply Likes
Roaming is 100% a client decision - when to roam and what to roam to is exclusively determined by the client.  APs can influence the roam but they cannot control it.  Try updating the client WiFi drivers or see if there is a roaming aggressiveness option in the driver settings. 

SmartRoam can be used in extreme cases, but in essence SmartRoam is simply disconnecting clients with a low signal so it may cause the client to miss some/lots of traffic if it's not very well written.

if all else fails, try to position the APs so the clients do not need to roam as they go about their business.