Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

Client is disconnected during 802.1x authentication attempt citing "Authentication Failure" for client disconnect reason

« Go Back

Information

 
TitleClient is disconnected during 802.1x authentication attempt citing "Authentication Failure" for client disconnect reason
Symptoms
  • Clients are unable to authenticate via 802.1x 
  • Controller receives Radius Accept for client, but client is immediately disconnected
  • Station Events log shows "Authentication Failure" for client disconnect reason
  • AP Log shows output:
Jan  4 21:05:12 hostapd1: 1483563912.005319: ath10: STA 28:18:78:d8:9b:5d IEEE 802.1X: authentication failed - EAP type: 0 ((null))
Jan  4 21:05:12 hostapd1: 1483563912.005694: ath10: STA 28:18:78:d8:9b:5d IEEE 802.1X: Supplicant used different EAP type: 25 ((null))
Jan  4 21:05:12 kernel: ieee80211_node_ap.c:182-_ieee80211_node_leave()-ath10 28:18:78:D8:9B:5D sta_assoc=1 ni=e73c6840 aid=1 wk_valid=0 keyix=65535 node_count=2 tm=4534 rss=-37
Jan  4 21:05:12 kernel: ieee80211_mlme.c:1580-ieee80211_mlme_recv_deauth()-ath10 triggers DEAUTH event 28:18:78:D8:9B:5D reason=3
Jan  4 21:05:12 hostapd1: 1483563912.016066: ath10: STA 28:18:78:d8:9b:5d IEEE 802.11: disassociated

 
Environment
  • Identifi
  • Firmware 10.11.04
Cause
Software
Resolution
Issue was not seen after upgrading to 10.21.01 (although there is no listing in release notes)
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255