IEEE 802.11 is a set of standards for wireless LANs, and it defines various codes that can be used to identify network issues. These codes are typically found in debug logs or network analyzer reports.
Understanding the Codes
This Reason Code field explains why certain network management messages, like Disassociation, Deauthentication, DELTS, DELBA, DLS Teardown, or Mesh Peering Close, were sent without being requested. It is part of the Mesh Channel Switch Parameters to show why the channel was switched. It is also part of the PERR element to explain why there was a path error.
Association Status Codes: These indicate the reason for a successful or unsuccessful association between a wireless device and an access point.
Deauthentication Reasons: These codes explain why a device was forcibly disconnected from a network.
Authentication Failures: These codes provide information about why authentication attempts failed.
Reason codes:
Reason codeMeaning1Unspecified reason2Previous authentication no longer valid3Deauthenticated because sending station is leaving (or has left) independent basic service set (IBSS) or extended service set (ESS)4Disassociated due to inactivity5Disassociated because access point (AP) unable to handle all currently associated stations6Class 2 frame received from nonauthenticated station7Class 3 frame received from nonassociated station8Disassociated because sending station is leaving (or has left) basic service set (BSS)9Station requesting association or reassociation not authenticated with responding station10Disassociated because of unacceptable information in the power capability element11Disassociated because of unacceptable information in the supported channels element13Invalid information (Doesn’t follow 802.11 standard)14Message integrity code (MIC) failure154-way handshake timeout16Group-key handshake timeout17Information element in 4-way handshake different from association request, reassociation request, probe response, or beacon frame18Invalid group cipher19Invalid pairwise cipher20Invalid authentication and key management protocol (AKMP)21Unsupported robust security network (RSN) information element version22Invalid RSN information element capabilities23IEEE 802.1X authentication failed24Cipher suite rejected because of security policy32Disassociated for unspecified quality of service (QoS)-related reason33Disassociated because QoS AP lacks sufficient bandwidth for this QoS station34Disassociated because excessive number of frames need to be acknowledged, but are not acknowledged due to AP transmissions or poor channel conditions, or both35Disassociated because station is transmitting outside limits of its transmission opportunities (TXOPs)36Requested from peer station as station is leaving or resetting the BSS37Requested from peer station as it doesn’t want to use the mechanism38Requested from peer station as station received frames using the mechanism for which a setup is required39Requested from peer station due to timeout45Peer station doesn’t support requested cipher suite
Association status codes:
Association status codes are numerical values included in an association response frame to indicate the outcome of an association request between a wireless client and an access point (AP). These codes provide crucial information about the success or failure of the association process, helping in troubleshooting connectivity issues.
Status codeMeaning0Successful1Unspecified failure2Tunneled direct link setup (TDLS) wakeup schedule rejected but alternative schedule provided3TDLS wakeup schedule rejected5Security disabled6Unacceptable lifetime7Not in same basic service set (BSS)10Can’t support all requested capabilities in capability information field11Reassociation denied due to inability to confirm that association exists12Association denied due to reason outside scope of this standard13Responding station doesn’t support specified authentication algorithm14Received authentication frame with authentication transaction sequence number out of expected sequence15Authentication rejected because of challenge failure16Authentication rejected due to timeout waiting for next frame in sequence17Association denied because AP unable to handle additional associated stations18Association denied due to requesting station not supporting all data rates in the BSSBasicRateSet parameter, where BSS refers to basic service set19Association denied due to requesting station not supporting short preamble option20Association denied due to requesting station not supporting packet binary convolutional code (PBCC) modulation option21Association denied due to requesting station not supporting channel agility option22Association request rejected because spectrum management capability required23Association request rejected because of unacceptable information in the power capability element24Association request rejected because of unacceptable information in the supported channels element25Association denied due to requesting station not supporting short slot time option26Association denied due to requesting station not supporting direct sequence spread spectrum orthogonal frequency division multiplexing (DSSS-OFDM) option27Association denied because requesting station doesn’t support high throughput (HT) features28Pairwise master key (PMK-R0) Key Holder (R0KH) unreachable29Association denied because requesting station doesn’t support phased coexistence operation (PCO) transition time required by the AP30Association request rejected temporarily; try again later31Robust management frame policy violation32Unspecified. Quality of service (QoS)-related failure33Association denied because QoS AP has insufficient bandwidth to handle another QoS station34Association denied due to excessive frame loss rates or poor conditions on current operating channel, or both35Association (with QoS BSS) denied because the requesting station does not support the QoS facility37Request declined38Request not successful as one or more parameters have invalid values39Traffic stream (TS) not created because request can’t be honored; however, suggested traffic specification (TSPEC) provided so that the initiating station may attempt to set another TS with suggested changes to TSPEC40Invalid information element (doesn’t follow 802.11 standard)41Invalid group cipher42Invalid pairwise cipher43Invalid authentication and key management protocol (AKMP)44Unsupported robust security network element (RSNE) information element version45Invalid RSNE information element capabilities46Cipher suite rejected because of security policy47TS not created; however, hybrid coordinator (HC) may be capable of creating TS, in response to a request, after the time indicated in TS delay element48Direct link not allowed in the BSS by policy49Destination station not present within this BSS50Destination station not a QoS station51Association denied because ListenInterval too large52Invalid fast transition (FT) action frame count53Invalid shared key (pairwise master key identifier or PMKID)54Invalid mobility domain element (MDE)55Invalid fast transition element (FTE)56Requested traffic classification (TCLAS) processing not supported by AP57AP has insufficient TCLAS processing resources to satisfy request58TS not created because request can’t be honored; however, HC suggests station transitions to other BSSs to set up TS59Generic advertisement service (GAS) advertisement protocol not supported60No outstanding GAS request61GAS response not received from advertisement server62Station timed out waiting for GAS query response63GAS response larger than query response length limit64Request refused because home network doesn’t support request65Advertisement server in network not currently reachable68Request refused because AP doesn’t support unauthenticated access73Unscheduled Automatic Power Save Delivery (U-APSD) coexistence not supported74Requested U-APSD coexistence mode not supported75Requested interval or duration value can’t be supported with U-APSD coexistence76Authentication rejected because anti-clogging token is required77Authentication rejected because the offered finite cyclic group not supported78The Target Beacon Transmission Time (TBTT) adjustment request not successful because station couldn’t find alternative TBTT79Transmission failure80Requested TCLAS not supported81TCLAS resources exhausted82Rejected with suggested BSS transition93Association or reassociation refused because of memory limits at AP94Association or reassociation refused because emergency services not supported at AP95GAS query response not yet received101Request failed due to exceeded MCCA access fraction (MAF) limit102Request failed due to exceeded MCF coordinated channel access (MCCA) track limit, where MCF refers to mesh coordination function
The post IEEE 802.11 Reason codes to identify network issues appeared first on WiFi.