Zyxel AP Event Log Guide: Interpreting Reason Codes and Descriptions

The article provides a detailed list of reason codes commonly found in access point event logs. These codes, ranging from 0 to 45, explain various disassociation and deauthentication scenarios, such as inactivity, insufficient bandwidth, invalid authentication, and security policy issues. Some codes are reserved, while others address specific technical issues like message integrity failures, invalid ciphers, and timeout requests. Understanding these codes helps in diagnosing network issues and improving connectivity.

You may often encounter reason codes (#) in event logs without fully understanding their meaning. Below are some common reason codes related to access point event logs:

Reason#Description
0Reserved
1Unspecific 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
14Message integrity code (MIC) failure
154-Way Handshake timeout
16Group Key Handshake timeout

 

Reason#Description
17Information element in 4-Way Handshake different from (Re)Association Request/Probe Response/Beacon frame
18Invalid group cipher or Association denied due to requesting STA not supporting all of the data rates in the BSSBasicRateSet parameter
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

 

Reason#Description
35Disassociated because STA is transmitting outside the limits of its TXOPs
36Requested from peer STA as the STA is leaving the BSS (or resetting)
37Requested from peer STA as it does not want to use the
38Requested from peer STA as the STA received frames using the mechanism for which a setup is required
39Requested from peer STA due to timeout
45Peer STA does not support the requested cipher sui

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share