Association response reason code :
Reason code field:
As you can see, some codes are irrelevant for an association response. That is because the reason code field has the same meaning wherever it is used (disassociation frames, …)
Status | Meaning |
0 | Success |
1 | Unspecified failure |
2-9 | Reserved |
10 | Cannot support all requested capabilities in the Capability Information field |
11 | Reassociation denied due to inability to confirm that association exists |
12 | Association denied due to reason outside the scope of this standard |
13 | Responding STA does not support the specified authentication algorithm |
14 | Received an Authentication frame with authentication transaction sequence number out of expected sequence |
15 | Authentication rejected because of challenge failure |
16 | Authentication rejected due to timeout waiting for next frame in sequence |
17 | Association denied because AP is unable to handle additional associated STAs |
18 | Association denied due to requesting STA not supporting all of the data rates in the BSSBasicRateSet parameter |
19 | Association denied due to requesting STA not supporting the short preamble option |
20 | Association denied due to requesting STA not supporting the PBCC modulation option |
21 | Association denied due to requesting STA not supporting the Channel Agility option |
22 | Association request rejected because Spectrum Management capability is required |
23 | Association request rejected because the information in the Power Capability element is unacceptable |
24 | Association request rejected because the information in the Supported Channels element is unacceptable |
25 | Association denied due to requesting STA not supporting the Short Slot Time option |
26 | Association denied due to requesting STA not supporting the DSSS-OFDM option |
27-31 | Reserved |
32 | Unspecified, QoS-related failure |
33 | Association denied because QoS AP has insufficient bandwidth to handle another QoS STA |
34 | Association denied due to excessive frame loss rates and/or poor conditions on current operating channel |
35 | Association (with QoS BSS) denied because the requesting STA does not support the QoS facility |
36 | Reserved |
37 | The request has been declined |
38 | The request has not been successful as one or more parameters have invalid values |
39 | The TS has not been created because the request cannot be honored; however, a suggested TSPEC is provided so that the initiating STA may attempt to set another TS with the suggested changes to the TSPEC |
40 | Invalid information element, i.e., an information element defined in this standard for which the content does not meet the specifications in Clause 7 |
41 | Invalid group cipher |
42 | Invalid pairwise cipher |
43 | Invalid AKMP |
44 | Unsupported RSN information element version |
45 | Invalid RSN information element capabilities |
46 | Cipher suite rejected because of security policy |
47 | The TS has not been created; however, the HC may be capable of creating a TS, in response to a request, after the time indicated in the TS Delay element |
48 | Direct link is not allowed in the BSS by policy |
49 | The Destination STA is not present within this BSS |
50 | The Destination STA is not a QoS STA |
51 | Association denied because the ListenInterval is too large
|
And for authentication frame :
As you can see, some codes are irrelevant for an association response. That is because the reason code field has the same meaning wherever it is used (deauthentication frames, …)
Reason code | Meaning |
1 | Unspecified reason |
2 | Previous authentication no longer valid |
3 | Deauthenticated because station leaving BSS/ESS |
4 | Disassociated due to inactivity |
5 | Disassociated because AP unable to handle all currently associated stations |
6 | Class 2 frame received from non authenticated station |
7 | Class 3 frame received from non associated station |
8 | Diassociated because station leaving BSS/ESS |
9 | Station requesting (re)association is not associated with the responding station. |
10 | Diassociated because the information in the power capability element is unacceptable |
11 | Disassociated because the information in the supported channels element in unacceptable |
12 | Reserved |
13 | Invalid information element (not matching standard format) |
14 | MIC failure |
15 | 4-way handshake timeout |
16 | Group key handshake timeout |
17 | Information element in 4 way handshake different from association request/probe response/beacon element |
18 | Invalid group cipher |
19 | Invalid pairwise cipher |
20 | Invalid AKMP |
21 | Unsupported RSN information element version number |
22 | Invalid RSN information element capabilities |
23 | 802.1x authentication failed |
24 | Cipher suite rejected because of security policy |
25-31 | Reserved |
32 | Diassociated for unspecified QoS related reason |
33 | Disassociated because QoS AP lacks sufficient bandwidth for QoS station |
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 | 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 mechanism |
38 | Requested from peer STA as the STA received frames using the mechanism for which a setup is required |
39 | Requested from peer station due to timeout |
45 | Peer station does not support the cipher suite |
