Code

Reason

Explanation

0

Reserved

Normal working operation

1

Unspecific Reason

We don’t know what’s wrong

2

Previous authentication no longer valid

Client has associated but is not authorised.

3

Deauthenticated because sending STA is leaving (or has left) IBSS or ESS

The access point went offline, deauthenticating the client.

4

Disassociated due to inactivity

Client session timeout exceeded.

5

Disassociated because AP is unable to handle all currently associated STAs

The access point is busy, performing load balancing, for example.

6

Class 2 frame received from nonauthenticated STA

Client attempted to transfer data before it was authenticated.

7

Class 3 frame received from nonassociated STA

Client attempted to transfer data before it was associated.

8

Disassociated because sending STA is leaving (or has left) BSS

Operating System moved the client to another access point using non-aggressive load balancing.

9

STA requesting (re)association is not authenticated with responding STA

Client not authorized yet, still attempting to associate with an access point.

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

Reserved

Not Used or Special Purpose

13

Invalid information element.

14

Message integrity code (MIC) failure

15

4-Way Handshake timeout

16

Group Key Handshake timeout

17

Information element in 4-Way Handshake different from (Re)Association Request/Probe
Response/Beacon frame

18

Invalid group cipher
or
Association denied due to requesting STA not supporting all of the data rates
in the BSSBasicRateSet parameter

*NEW*
The link speed requested by the client or AP is incompatible. (i,e. trying to
operate N only speeds on a G AP)

19

Invalid pairwise cipher

20

Invalid AKMP

21

Unsupported RSN information element version

22

Invalid RSN information element capabilities

23

IEEE 802.1X authentication failed

24

Cipher suite rejected because of the security policy

25-31

Reserved

Not Used or Special Purpose

32

Disassociated for unspecified, QoS-related reason

Quality of Service has denied the action.

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

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 STA due to timeout

45

Peer STA does not support the requested cipher suite

45-65

Reserved

Not Used or Special Purpose

99

Typically “No Reason Code” / Unknown State

535

Reserved

Not Used or Special Purpose

The first few reason codes where helpful
while debugging my wifi related issues.

Linux WiFi Deauthenticated Reason Codes的更多相关文章

  1. kali linux wifi破解(aircrack)

    需要一个能监听的网卡 airmon-ng start wlan0(監聽網卡) airmon-ng check kill(清除其他有影响的環境) airodump-ng mon0 (掃描附近wifi) ...

  2. linux wifi热点服务脚本

    最近有关wifi热点的驱动,启动参数都调试完了,验证可以连接传输数据. 首先要在系统启动脚本中插入wifi驱动,配置wlan0的ip insmod /system/vendor/modules/818 ...

  3. Linux Wifi模块灰色解决办法

    https://www.cnblogs.com/mcy0808/p/5415689.html -sudo gedit /etc/rc.local 连上了CUG但还是打不开网页,是不是需要编辑Conne ...

  4. Linux网络驱动--snull

    snull是<Linux Device Drivers>中的一个网络驱动的例子.这里引用这个例子学习Linux网络驱动. 因为snull的源码,网上已经更新到适合最新内核,而我自己用的还是 ...

  5. Smart210学习记录------linux串口驱动

    转自:http://blog.chinaunix.net/xmlrpc.php?r=blog/article&uid=27025492&id=327609 一.核心数据结构 串口驱动有 ...

  6. Introduction the naive“scull” 《linux设备驱动》 学习笔记

    Introduction the naive "scull" 首先.什么是scull? scull (Simple Character Utility for Loading Lo ...

  7. 【从零开始,从内核驱动驱动到用户空间调用】编写第一个linux驱动,通过端口访问I/O寄存器。

    目的: 通过I/O端口方式访问RTC的秒寄存器: 由于本人从来没看过linux方面的书籍,也只是会在终端用些常用的命令而已,这次老大叫我学着通过I/O端口方式直接去读写寄存器.于是我在google中搜 ...

  8. Android KitKat 4.4 Wifi移植之Wifi driver

    本文讲述在Linux 3.10下Realek RTL8723A Linux Wifi 驱动的移植. Prerequisites 硬件平台:Atmel SAMA5 软件平台:Linux 3.10 + A ...

  9. zynq linux驱动之PL-PS中断【转】

    转自:https://blog.csdn.net/h244259402/article/details/83993524 PC:Windows 10 虚拟机:ubuntu 16.04 vivado:2 ...

随机推荐

  1. 20145208蔡野 《网络对抗》逆向及BOF基础实践

    20145208蔡野 <网络对抗>逆向及BOF基础实践 逆向及Bof基础实践 实践目标 本次实践的对象是一个名为pwn1的linux可执行文件. 该程序正常执行流程是:main调用foo函 ...

  2. noip2008 真题练习 2017.2.25

    不是有很多可以说的,记住不能边算边取min Code #include<iostream> #include<fstream> #include<sstream> ...

  3. Android学习笔记之 ActionBar

    http://developer.android.com/guide/topics/ui/actionbar.html 1,ActionBar的几种形式 2,使用ActionBar需要Activity ...

  4. Linux slab分配器【转】

    本文转载自:https://www.ibm.com/developerworks/cn/linux/l-linux-slab-allocator/ 良好的操作系统性能部分依赖于操作系统有效管理资源的能 ...

  5. 在ubuntu bionic下对基于qemu的arm64进行linux内核5.0.1版本的编译和运行

    一.环境介绍 OS:ubuntu bionic 64bit 二.准备工作 2.1 安装必要的开发工具 sudo apt-get install git flex bison build-essenti ...

  6. HDU 6148 Valley Numer (数位DP)题解

    思路: 只要把status那里写清楚就没什么难度T^T,当然还要考虑前导零! 代码: #include<cstdio> #include<cstring> #include&l ...

  7. hdu 3874(树状数组)题解

    Problem Description Mery has a beautiful necklace. The necklace is made up of N magic balls. Each ba ...

  8. 【Android实验】组件通信Intent

    实验目的 [TOC] 了解使用Intent进行组件通信原理 掌握使用Intent启动Activity的方法 熟悉和掌握Android组件间通信的方式和技巧 实验要求 设计一个主Activity和一个子 ...

  9. python urljoin问题

    如何去除url拼接的时候存在的遗留的'../'问题,可以参考如下的强制去除方法: def fix_URL(urlstring): parts = list(urlparse.urlparse(urls ...

  10. SetCommMask

    SetCommMask           用途:设置串口通信事件   原型:BOOL SetCommMask(HANDLE hFile, //标识通信端口的句柄   DWORD dwEvtMask ...