Wireless Frame Management Deauthorization Codes
The following list of Wireless Deauthorization codes will give you some help in troubleshooting why a certain wireless device disassociated from an access point. If you are troubleshooting an access point dropping out mysteriously, or are just doing audits of your access point logs, these should provide some clarity to that.
Client Reason Code – Description – Meaning
- 0 – noReasonCode – Normal operation.
- 1 – unspecifiedReason – Client associated but no longer authorized.
- 2 – previousAuthNotValid – Client associated but not authorized.
- 3 – deauthenticationLeaving – The access point went offline, deauthenticating the client.
- 4 – disassociationDueToInactivity – Client session timeout exceeded.
- 5 – disassociationAPBusy – The access point is busy, performing load balancing, for example.
- 6 – class2FrameFromNonAuthStation – Client attempted to transfer data before it was authenticated.
- 7 – class2FrameFromNonAssStation – Client attempted to transfer data before it was associated.
- 8 – disassociationStaHasLeft – Operating System moved the client to another access point using non-aggressive load balancing.
- 9 – staReqAssociationWithoutAuth – Client not authorized yet, still attempting to associate with an access point.
- 99 – missingReasonCode – Client momentarily in an unknown state.

When setting up your own domain name for Google Apps or Google Hosted Email service, Google only provides you with 5 MX records and values. It turns out, they have 3 more for a total of 8.