zf2942 client disassociate for reason 8 or 14 something have a solution

  • 1
  • Question
  • Updated 8 months ago
this is the log
Dec 16 14:42:17 RuckusAP daemon.warn Eved: STA-DISASSOC-REASON,nimac=30:75:12:e3:7e:df,func=domlme,line=5567,hint=domlme,rx_rssi=14,ack_rssi=0,reason=14,freq=2462,chan=11,stats=(10,915,6,690)Dec 16 14:42:17 RuckusAP daemon.info hostapd: wlan0: STA 30:75:12:e3:7e:df IEEE 802.11: disassociated
Dec 16 14:42:17 RuckusAP daemon.warn Eved: STA-DISASSOC-REASON,nimac=d0:87:e2:24:0e:f8,func=domlme,line=5567,hint=domlme,rx_rssi=23,ack_rssi=0,reason=14,freq=2462,chan=11,stats=(145,21361,155,38703)
Dec 16 14:42:17 RuckusAP daemon.warn Eved: STA-DISASSOC-REASON,nimac=a0:e4:53:be:88:1b,func=domlme,line=5567,hint=domlme,rx_rssi=16,ack_rssi=0,reason=14,freq=2462,chan=11,stats=(30,2815,96,9280)
Dec 16 14:42:18 RuckusAP daemon.warn Eved: STA-DISASSOC-REASON,nimac=b4:8b:19:91:17:4d,func=domlme,line=5567,hint=domlme,rx_rssi=34,ack_rssi=0,reason=14,freq=2462,chan=11,stats=(2774,289311,3963,5157738)
Dec 16 14:42:18 RuckusAP daemon.warn Eved: STA-DISASSOC-REASON,nimac=40:b8:37:ab:b4:a5,func=domlme,line=5567,hint=domlme,rx_rssi=23,ack_rssi=0,reason=14,freq=2462,chan=11,stats=(487,61955,559,174035)
Dec 16 14:42:18 RuckusAP daemon.warn Eved: STA-DISASSOC-REASON,nimac=00:02:78:60:94:61,func=domlme,line=5567,hint=domlme,rx_rssi=41,ack_rssi=0,reason=14,freq=2462,chan=11,stats=(2,205,0,0)
Dec 16 14:42:18 RuckusAP daemon.info hostapd: wlan0: STA d0:87:e2:24:0e:f8 IEEE 802.11: disassociated
Dec 16 14:42:18 RuckusAP daemon.info hostapd: wlan0: STA a0:e4:53:be:88:1b IEEE 802.11: disassociated
Dec 16 14:42:18 RuckusAP daemon.info hostapd: wlan0: STA b4:8b:19:91:17:4d IEEE 802.11: disassociated
Dec 16 14:42:18 RuckusAP daemon.info hostapd: wlan0: STA 40:b8:37:ab:b4:a5 IEEE 802.11: disassociated
Dec 16 14:42:18 RuckusAP daemon.info hostapd: wlan0: STA 00:02:78:60:94:61 IEEE 802.11: disassociated
Dec 16 14:43:17 RuckusAP daemon.info hostapd: wlan0: IEEE 802.11 TKIP countermeasures ended
Dec 16 14:43:20 RuckusAP daemon.info hostapd: wlan0: STA 00:02:78:60:94:61 IEEE 802.11: associated
Dec 16 14:43:20 RuckusAP daemon.info hostapd: wlan0: STA 00:02:78:60:94:61 WPA: pairwise key handshake completed (RSN)
Dec 16 14:43:21 RuckusAP daemon.info hostapd: wlan0: STA d0:87:e2:24:0e:f8 IEEE 802.11: associated
Dec 16 14:43:21 RuckusAP daemon.info hostapd: wlan0: STA d0:87:e2:24:0e:f8 WPA: pairwise key handshake completed (RSN)
Dec 16 14:43:36 RuckusAP daemon.info hostapd: wlan0: STA 40:b8:37:ab:b4:a5 IEEE 802.11: associated
Dec 16 14:43:36 RuckusAP daemon.info hostapd: wlan0: STA 40:b8:37:ab:b4:a5 WPA: pairwise key handshake completed (RSN)
Dec 16 14:46:29 RuckusAP daemon.info hostapd: wlan0: STA 30:75:12:e3:7e:df IEEE 802.11: associated
Dec 16 14:46:29 RuckusAP daemon.info hostapd: wlan0: STA 30:75:12:e3:7e:df WPA: pairwise key handshake completed (RSN)
Dec 16 14:54:14 RuckusAP daemon.info hostapd: wlan0: STA a0:e4:53:be:88:1b IEEE 802.11: associated
Dec 16 14:54:14 RuckusAP daemon.info hostapd: wlan0: STA a0:e4:53:be:88:1b WPA: pairwise key handshake completed (RSN)
Dec 16 15:04:05 RuckusAP user.warn kernel: wifi0: 510190433: stuck beacon; resetting (bmiss count 10) scanning 0, syncbeacon 0, sc_beacons 1 nf(-100) new(-90)
Photo of Stephane Lanfrey

Stephane Lanfrey

  • 1 Post
  • 0 Reply Likes

Posted 8 months ago

  • 1
Photo of Big Dog

Big Dog

  • 58 Posts
  • 9 Reply Likes
Mhhh it's an old one ! (E.O.L)
What version of firmware do you use?