What are the different Reason Codes that can be seen in the 802.11 frames and their meanings?

Aruba Employee
Q:

What are the different Reason Codes that can be seen in the 802.11 frames and their meanings?  

What are the meanings for the different Reason Codes found in the Deauthentication and Disassociation packets? 

 



A:

The Reason Code field is used to indicate the reason that an unsolicited notification management frame of type Disassociation, Deauthentication, DELTS, DELBA, DLS Teardown, or Mesh Peering Close was generated. 
Below is the list of all Reason Codes as per IEEE Std 802.11-2012 Section 8.4.1.7 Reason Code field - Table 8-36. 

 

Reason Code  Name  Meaning 
0   Reserved
1   Unspecified 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   Disassociated due to BSS Transition Management
13   Invalid element, i.e., an element defined in this standard for which the content does not meet the specifications in Clause 8
14   Message integrity code (MIC) failure
15   4-Way Handshake timeout
16   Group Key Handshake timeout
17   element in 4-Way Handshake different from (Re)Association Request/Probe Response/Beacon frame
18   Invalid group cipher
19   Invalid pairwise cipher
20   Invalid AKMP
21   Unsupported RSNE version
22   Invalid RSNE capabilities
23   IEEE 802.1X authentication failed
24   Cipher suite rejected because of the security policy
25   TDLS direct-link teardown due to TDLS peer STA unreachable via the TDLS direct link
26   TDLS direct-link teardown for unspecified reason
27   Disassociated because session terminated by SSP request
28   Disassociated because of lack of SSP roaming agreement
29   Requested service rejected because of SSP cipher suite or AKM requirement
30   Requested service not authorized in this location
31 SERVICE_CHANGE_PRECLUDES_TS TS deleted because QoS AP lacks sufficient bandwidth for this QoS STA due to a change in BSS service characteristics or operational mode (e.g., an HT BSS change from 40 MHz channel to 20 MHz channel)
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
35   Disassociated because STA is transmitting outside the limits of its TXOPs
36 STA_LEAVING STA_LEAVING Requested from peer STA as the STA is leaving the BSS (or resetting)
37 END_TS
END_BA
END_DLS
Requested from peer STA as it does not want to use the mechanism
38 UNKNOWN_TS
UNKNOWN_BA
Requested from peer STA as the STA received frames using the mechanism for which a setup is required
39 TIMEOUT Requested from peer STA due to timeout
45 PEERKEY_MISMATCH Peer STA does not support the requested cipher suite
46 PEER_INITIATED In a DLS Teardown frame: The teardown was initiated by the DLS peer. In a Disassociation frame: Disassociated because authorized access limit reached
47 AP_INITIATED In a DLS Teardown frame: The teardown was initiated by the AP. In a Disassociation frame: Disassociated due to external service requirements
48   Invalid FT Action frame count
49   Invalid pairwise master key identifier (PMKI)
50   Invalid MDE
51   Invalid FTE
52 MESH-PEERING-CANCELLED SME cancels the mesh peering instance with the reason other than reaching the maximum number of peer mesh STAs
53 MESH-MAX-PEERS The mesh STA has reached the supported maximum number of peer mesh STAs
54 MESH-CONFIGURATION-POLICY-VIOLATION The received information violates the Mesh Configuration policy configured in the mesh STA profile
55 MESH-CLOSE-RCVD The mesh STA has received a Mesh Peering Close message requesting to close the mesh peering.
56 MESH-MAX-RETRIES The mesh STA has resent dot11MeshMaxRetries Mesh Peering Open messages, without receiving a Mesh Peering Confirm message.
57 MESH-CONFIRM-TIMEOUT The confirmTimer for the mesh peering instance times out.
58 MESH-INVALID-GTK The mesh STA fails to unwrap the GTK or the values in the wrapped contents do not match
59 MESH-INCONSISTENT-PARAMETERS The mesh STA receives inconsistent information about the mesh parameters between Mesh Peering Management frames 
60 MESH-INVALID-SECURITY-CAPABILITY The mesh STA fails the authenticated mesh peering exchange because due to failure in selecting either the pairwise ciphersuite or group ciphersuite
61 MESH-PATH-ERROR-NO-PROXY-INFORMATION The mesh STA does not have proxy information for this external destination.
62 MESH-PATH-ERROR-NO-FORWARDING-INFORMATION The mesh STA does not have forwarding information for this destination.
63 MESH-PATH-ERROR-DESTINATION-UNREACHABLE The mesh STA determines that the link to the next hop of an active path in its forwarding information is no longer usable.
64 MAC-ADDRESS-ALREADY-EXISTS-IN-MBSS The Deauthentication frame was sent because the MAC address of the STA already exists in the mesh BSS. See 10.3.6.
65 MESH-CHANNEL-SWITCH-REGULATORY-REQUIREMENTS The mesh STA performs channel switch to meet regulatory requirements.
66 MESH-CHANNEL-SWITCH-UNSPECIFIED The mesh STA performs channel switch with unspecified reason.
67–65535   Reserved

 

 

 
Version history
Revision #:
2 of 2
Last update:
‎11-25-2015 04:17 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: