Access Point Event Log Reason Code and Descriptions


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 |
---|---|
0 | Reserved |
1 | Unspecific Reason |
2 | Previous authentication no longer valid |
3 | Deauthenticated because sending STA is leaving (or has left) IBSS or ESS |
4 | Disassociated due to inactivity |
5 | Disassociated because AP is unable to handle all currently associated STAs |
6 | Class 2 frame received from nonauthenticated STA |
7 | Class 3 frame received from nonassociated STA |
8 | Disassociated because sending STA is leaving (or has left) BSS |
9 | STA requesting (re)association is not authenticated with responding STA |
10 | Disassociated because the information in the Power Capability element is unacceptable |
11 | Disassociated because the information in the Supported Channels element is unacceptable |
12 | Reserved |
13 | Invalid information element |
14 | Message integrity code (MIC) failure |
15 | 4-Way Handshake timeout |
16 | Group Key Handshake timeout |
Reason# | Description |
---|---|
17 | Information element in 4-Way Handshake different from (Re)Association Request/Probe Response/Beacon frame |
18 | Invalid group cipher or Association denied due to requesting STA not supporting all of the data rates in the BSSBasicRateSet parameter |
19 | Invalid pairwise cipher |
20 | Invalid AKMP |
21 | Unsupported RSN information element version |
22 | Invalid RSN information element capabilities |
23 | IEEE 802.1X authentication failed |
24 | Cipher suite rejected because of the security policy |
25-31 | Reserved |
32 | Disassociated for unspecified, QoS-related reason |
33 | Disassociated because QoS AP lacks sufficient bandwidth for this QoS STA |
34 | Disassociated because excessive number of frames need to be acknowledged, but are not acknowledged due to AP transmissions and/or poor channel conditions |
Reason# | Description |
---|---|
35 | Disassociated because STA is transmitting outside the limits of its TXOPs |
36 | Requested from peer STA as the STA is leaving the BSS (or resetting) |
37 | Requested from peer STA as it does not want to use the |
38 | Requested from peer STA as the STA received frames using the mechanism for which a setup is required |
39 | Requested from peer STA due to timeout |
45 | Peer STA does not support the requested cipher sui |
Categories
- All Categories
- 417 Beta Program
- 2.5K Nebula
- 160 Nebula Ideas
- 108 Nebula Status and Incidents
- 5.9K Security
- 331 USG FLEX H Series
- 286 Security Ideas
- 1.5K Switch
- 78 Switch Ideas
- 1.2K Wireless
- 42 Wireless Ideas
- 6.6K Consumer Product
- 259 Service & License
- 402 News and Release
- 86 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.8K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 80 Security Highlight