Status code |
Meaning |
0 |
Successful |
1 |
Unspecified failure |
2 |
Tunneled direct link setup (TDLS) wake-up schedule rejected but alternative schedule provided |
3 |
TDLS wake-up schedule rejected |
5 |
Security disabled |
6 |
Unacceptable lifetime |
7 |
Not in same basic service set (BSS) |
10 |
Can't support all requested capabilities in capability information field |
11 |
Re-association denied due to inability to confirm that association exists |
12 |
Association denied due to reason outside scope of this standard |
13 |
Responding station doesn't support specified authentication algorithm |
14 |
Received 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 unable to handle additional associated stations |
18 |
Association denied due to requesting station not supporting all data rates in the BSSBasicRateSet parameter, where BSS refers to basic service set |
19 |
Association denied due to requesting station not supporting short preamble option |
20 |
Association denied due to requesting station not supporting packet binary convolutional code (PBCC) modulation option |
21 |
Association denied due to requesting station not supporting channel agility option |
22 |
Association request rejected because spectrum management capability required |
23 |
Association request rejected because of unacceptable information in the power capability element |
24 |
Association request rejected because of unacceptable information in the supported channels element |
25 |
Association denied due to requesting station not supporting short slot time option |
26 |
Association denied due to requesting station not supporting direct sequence spread spectrum orthogonal frequency division multiplexing (DSSS-OFDM) option |
27 |
Association denied because requesting station doesn't support high throughput (HT) features |
28 |
Pairwise master key (PMK-R0) Key Holder (R0KH) unreachable |
29 |
Association denied because requesting station doesn't support phased coexistence operation (PCO) transition time required by the AP |
30 |
Association request rejected temporarily; try again later |
31 |
Robust management frame policy violation |
32 |
Unspecified. Quality of service (QoS)-related failure |
33 |
Association denied because QoS AP has insufficient bandwidth to handle another QoS station |
34 |
Association denied due to excessive frame loss rates or poor conditions on current operating channel, or both |
35 |
Association (with QoS BSS) denied because the requesting station does not support the QoS facility |
37 |
Request declined |
38 |
Request not successful as one or more parameters have invalid values |
39 |
Traffic 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 TSPEC |
40 |
Invalid information element (doesn't follow 802.11 standard) |
41 |
Invalid group cipher |
42 |
Invalid pairwise cipher |
43 |
Invalid authentication and key management protocol (AKMP) |
44 |
Unsupported robust security network element (RSNE) information element version |
45 |
Invalid RSNE information element capabilities |
46 |
Cipher suite rejected because of security policy |
47 |
TS not created; however, hybrid coordinator (HC) may be capable of creating TS, in response to a request, after the time indicated in TS delay element |
48 |
Direct link not allowed in the BSS by policy |
49 |
Destination station not present within this BSS |
50 |
Destination station not a QoS station |
51 |
Association denied because ListenInterval too large |
52 |
Invalid fast transition (FT) action frame count |
53 |
Invalid pairwise master key identifier (PMKID) |
54 |
Invalid mobility domain element (MDE) |
55 |
Invalid fast transition element (FTE) |
56 |
Requested traffic classification (TCLAS) processing not supported by AP |
57 |
AP has insufficient TCLAS processing resources to satisfy request |
58 |
TS not created because request can't be honored; however, HC suggests station transitions to other BSSs to set up TS |
59 |
Generic advertisement service (GAS) advertisement protocol not supported |
60 |
No outstanding GAS request |
61 |
GAS response not received from advertisement server |
62 |
Station timed out waiting for GAS query response |
63 |
GAS response larger than query response length limit |
64 |
Request refused because home network doesn't support request |
65 |
Advertisement server in network not currently reachable |
68 |
Request refused because AP doesn't support unauthenticated access |
73 |
Unscheduled Automatic Power Save Delivery (U-APSD) coexistence not supported |
74 |
Requested U-APSD coexistence mode not supported |
75 |
Requested interval or duration value can't be supported with U-APSD coexistence |
76 |
Authentication rejected because anti-clogging token is required |
77 |
Authentication rejected because the offered finite cyclic group not supported |
78 |
The Target Beacon Transmission Time (TBTT) adjustment request not successful because station couldn't find alternative TBTT |
79 |
Transmission failure |
80 |
Requested TCLAS not supported |
81 |
TCLAS resources exhausted |
82 |
Rejected with suggested BSS transition |
93 |
Association or re-association refused because of memory limits at AP |
94 |
Association or re-association refused because emergency services not supported at AP |
95 |
GAS query response not yet received |
101 |
Request failed due to exceeded MCCA access fraction (MAF) limit |
102 |
Request failed due to exceeded MCF coordinated channel access (MCCA) track limit, where MCF refers to mesh coordination function |
Comments
0 comments
Please sign in to leave a comment.