Error for wireless request set mode 8b06 set failed on device wlan0 operation not supported

@Blamo27 the adapter you mean? I use the WN722N V2, but I’m thinking about just buying a new one which works without the hassle

Yeah me too I’ve the same problem, nothing to do..
=> I bought the ALFA AWUS036ACH

Which version of Kali did you try? I tried on Kali 2017.3 and it didn’t work either.

Hello,
I had the same issue.
I am using TP-Link WN722N.
Was it a hardware or software issue.
If software issue any idea will it be fixed?

@fire-fly Hi, it’s software. If you bought WN722N V1 you should be fine, but I don’t think V2 will be fixed anytime soon. I bought the same device as @Blamo27 and it works fine.

@rlphkrs What is your kernel version ? And your driver ?

I have the same problem with TL-wn722n_v3 what a waste of time and money.

I managed to get a TL-wn722n_v3 into monitor mode using this driver https://github.com/kimocoder/rtl8188eus, forgot to check the version before buying, it just saved my day.
I’m using Kali 2018.4 kernel 4.18.0

I have TP-Link TL-WN725N and i am getting this error «»Error for wireless request «Set Mode» (8B06) : SET failed on device wlan0 ; Invalid argument»».
I’m trying to enable monitor mode…
Does this support monitor mode??

Hi, Can anyone help to set TP-LINK TN-WN722N V3, on Monitor mode. I have tried many ways but unable to make it. Can anyone please help in resolving this.

Hi, Can anyone help to set TP-LINK TN-WN722N V3, on Monitor mode. I have tried many ways but unable to make it. Can anyone please help in resolving this.

Hi, I am a newbie. I’ve been trying to figure out the same problem like yours for months. The only difference for usb-wifi adapter, mine is TL-WN725n V3. I couldn’t get the interface in Monitor mode but weirdly enough I could still get internet connected through it. Luckily this guy saves my day. I tried to remove old driver that I gathered from various version in github. And started to reinstall new driver which recommended by jocahamilton in his post: https://github.com/kimocoder/rtl8188eus . Yes, it finally worked!!! I got the monitor mode. Maybe you can try out, probably it might worked for you as well.

Can any solve this problem
ERROR:: wireless request «Set Mode»(8B06) :
SET failed on device(name of the device); Operation not supported.

same here. i use TP-LINK TL-WN725N on kali linux on virtual box and everytime i set the monitor mode i got this error ERROR:: wireless request «Set Mode»(8B06) :
SET failed on device(name of the device); Invalid argument.

anybody can resolve this?

Guys please help me out i’ve struggled for more than 2 weeks now with this problem

Error for wireless request «Set Mode» (8B06) :
SET failed on device wlan0 ; Operation not permitted.

I have tried anything and now i’m just stuck.

i have got this error too before i managed my kali linux to recognize wifi
connection by plugging in a wireless adapter plus installing the driver.

are you struggling on kali linux on virtual machine?

…

I managed to get a TL-wn722n_v3 into monitor mode using this driver https://github.com/kimocoder/rtl8188eus, forgot to check the version before buying, it just saved my day.
I’m using Kali 2018.4 kernel 4.18.0

Yes with the drivers above monitor mode works on ubuntu 4.15.0-96-generic this this way:
ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up

error for wireless request set mode (8b06) set failed on device wlan0 invalid argument
ماسبب ظهور تلك المشكله في الفا Awus036ach

Correct, this same issue I had with the wrong driver installed. Try this one. https://github.com/kimocoder/rtl8188eus

error for wireless request set mode (8b06) set failed on device wlan0 invalid argument
ماسبب ظهور تلك المشكله في الفا Awus036ach

Still no solution for this issue ?

• Installed Kali on my asus laptop:
  5.6.0-kali2-amd64 nl80211: Driver does not support authentication/association or connect commands #1 SMP Debian 5.6.14-1kali1 (2020-05-25) x86_64 GNU/Linux
• Using AWUS036ACH
• Compiled 8812au driver from actual aircrack stable branch:
  https://github.com/aircrack-ng/rtl8812au
• System refuses to switch interface to monitor mode:
  Error for wireless request «Set Mode» (8B06) :
  SET failed on device wlan1 ; Operation not permitted.

I have this
Linux kali 5.6.0-kali2-amd64 #1 SMP Debian 5.6.14-1kali1 (2020-05-25) x86_64 GNU/Linux
and AWUS036ACH
I tried what satishcse said and it works 👏
thanks

Guys please help me out i’ve struggled for more than 2 weeks now with this problem

Error for wireless request «Set Mode» (8B06) :
SET failed on device wlan0 ; Operation not permitted.

I have tried anything and now i’m just stuck.

Same problem please help

Problem solved by for my AWUS036ACH on latest Kali Linux by installing driver RT8812au v5.7.0 branch:
https://github.com/aircrack-ng/rtl8812au/tree/v5.7.0

Follow install instruction:
$ sudo apt-get install dkms
$ sudo ./dkms-install.sh

Then, set monitor mode:
$ sudo iwconfig wlan1 mode monitor

All aircrack-ng suite works perfectly fine.

Hello , i have a problem in the second step in fluxion for to create a «captive portal » this message appears when I select my wifi card :
] Select an interface for the access point.

[1] eth0 [+] Intel Corporation 8254EM Gigabite Ethernet Controller(rev
[2] wlan0 [+] TP-Link TL-WN722N v2
[3] Repeat
[4] Back

[fluxion2@kali]-[~] 2

[*] Unable to start captive portal interface, returning!

can someone Help please?

iwconfig wlan0 mode managed
Error for wireless request «Set Mode» (8B06) :
SET failed on device wlan0 ; Operation not permitted.

if You are getting this error it means you are already in manged mode. sometime you set it into monitor mode but if wifi adapter physically eject by little push then it will again back to the managed mode. At the same time if you are trying to make it manage then it gives error because it is already in managed.

Having Kali in Virtual Box on Windows 10. Updating drivers for my Wi-Fi adapter on Windows 10 fixed issue.

I also personally use this adapter TLWN722N and I’ve faced the same issue
Error for wireless request «Set Mode» (8B06) :
SET failed on device wlan0 ; Operation not permitted.

To solve this issue you’ll need to set mode to auto by running the following commands :-
sudo ifconfig wlan0 down
sudo iwconfig wlan0 mode auto
sudo ifconfig wlan0 up
sudo iwconfig

After running these commands restart your machine

NOTE:- Always set to auto mode before shutting down your computer or else you’ll face the same issue

any blacklisted module/driver in /etc/modprobe.d/ ?

Thanks NabeelJiwani but the problem is that i don’t know what to do next.

My problem is, when I shut down my virtual machine and make the iwconfig wlan0 auto before I shut down my machine the error in the next session appears again. And when I see this error I just want to break everting near me.

Just sharing my finding:

I was getting the same error (Set Mode (8B06)) when running the «iwconfig wlan1 mode monitor» command.
However, I was able to fix/workaround it by bringing the adapter interface up then down again then setting to monitor mode. Not sure what is causing the issue but this seems to fix it (for me anyway)…

Here are the commands:
ifconfig wlan1 up
ifconfig wlan1 down
iwconfig wlan1 mode monitor

Notes:

• Using AWUS036ACH
• Screenshot attached to illustrate
• Didn’t read all comments

Hoping this might save someone time.

I just used command sudo apt-get install dkms
and its working fine now

I’m also using TL-WN722N ((V2/V3) and I also intermittently experience the same problem. This is how I solve it… with your adapter still plugged-in:
rmmod r8188eu.ko
modprobe 8188eu
Disconnect your adapter and reconnect. Now you should be able to put it in monitor mode. If it still fails, put it to auto mode first, down it, and now put it to monitor mode.

I’m also using TL-WN722N ((V2/V3) and I also intermittently experience the same problem. This is how I solve it… with your adapter still plugged-in:
rmmod r8188eu.ko
modprobe 8188eu
Disconnect your adapter and reconnect. Now you should be able to put it in monitor mode. If it still fails, put it to auto mode first, down it, and now put it to monitor mode.

Thank you! You just help me tremendously. I signed up with GitHub because of you.

Same issue with RasPi on 3+ — Recompiled with «apt install raspberrypi-kernel-headers» but still have to put it down and up..? Why is it doing that remain a mystery to me :/

I’m also using TL-WN722N ((V2/V3) and I also intermittently experience the same problem. This is how I solve it… with your adapter still plugged-in:
rmmod r8188eu.ko
modprobe 8188eu
Disconnect your adapter and reconnect. Now you should be able to put it in monitor mode. If it still fails, put it to auto mode first, down it, and now put it to monitor mode.

finally someone who knows a solution,this has been wreaking havoc for me,THIS IS THE FIRST STEP IN HACKING and it wouldn’t even work,thank you

Sudo iwconfig wlan0 mode monitor
Sudo iwconfig

I can’t believe this thread is still alive, but if you are still encountering this problem this may work for you.

1. take out your adapter
2. sudo rmmod r8188eu.ko
3. put your adapter back in
4. sudo modprobe 8188eu
5. sudo airmon-ng start wlan0

• note* the above command may not work, use iwconfig to check your adapter’s name.*
  6.iwconfig
  you should now be in monitor mode, congrats
  if somehow your are still in auto or managed mode:

1. put your adapter back in
2. ifconfig wlan0 up
3. ifconfig wlan0 down
4. now redo everything mentioned in the beginning
5. this worked for me, but everything is case-sensitive.

-josh

Good I’m using a tp link wn823n having the right drivers I get when trying to put the monitor mode with the command airmon-ng start wlan0 and then iwconfig I get manager mode instead of monitor mode and I’ve been trying the commands of the thread and I get the same error and I do not know what to do, if someone can help me. This image is an example but with all commands I get the same error

Hi ArturovI9,

Insert your network adapter first:

1. ifconfig wlan0 up

2. ifconfig wlan0 down

«Take out the network adapter»:

1. sudo rmmod r8188eu.ko

«Insert your network adapter»:

1. sudo modprobe 8188eu

2. iwconfig wlan0 mode monitor

Now, your network adapter should be in monitor mode, again lots of adapters no longer work with kali Linux, also make sure you have the proper drivers installed, and that your adapter is capable of monitor mode.

-Happy Hacking, josh

you don’t need to use airmon-ng at all. you can simply:

sudo ifconfig wlan0 down

than go on with

sudo iwconfig wlan0 mode monitor

and finally

sudo ifconfig wlan0 up

thats basically what airmon-ng does.

answered Jul 15, 2015 at 19:41

You need to read more about how to use aircrack-ng.

The command you executed, sudo airodump-ng mon0, tells your computer to start capturing packets on the interface called mon0, but you don’t have that interface yet, that’s why it tells you No such device.

The general steps in using aircrack-ng is:

1. sudo airmon-ng start wlan0

   • This puts your wireless interface into monitor mode, which is the mode where you can capture all packets, even if they weren’t directed to your computer. What the command actually does is it creates another interface called mon0, which you can see when you do iwconfig. This is the command that you probably didn’t execute. If you did run it but you can’t see mon0 afterwards, let us know what was the command’s output.

2. sudo airodump-ng <options> mon0

   • This starts capturing packets.

3. sudo aireplay-ng <options> mon0

   • You use this to attempt to increase the number of IVs being captured so you can easily crack the password.

4. sudo aircrack-ng <options> <file>

   • This is the application that then cracks the capture you took to extract the password.

answered Nov 13, 2014 at 4:22

The problem is with the name of the interface. Use the following commands:

Start your wireless interface in monitoring mode

airmon-ng   

Kill all the interfering processes

airmon-ng check kill     

Instead of airodump-ng mon0, type this airodump-ng wlan0mon

Please let me know if this works for you.

SidahmedSidahmed

1,0462 gold badges14 silver badges27 bronze badges

Code: Select all

:~$ inxi -Fxxxrz
System:
  Kernel: 5.4.0-77-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.8.6 info: plank wm: muffin 4.8.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:
  Type: Portable System: Dell product: Vostro 2520 v: N/A serial: <filter> 
  Chassis: type: 8 serial: <filter> 
  Mobo: Dell model: 0V1NDP v: A11 serial: <filter> BIOS: Dell v: A11 
  date: 02/24/2014 
CPU:
  Topology: Dual Core model: Intel Core i3-2328M bits: 64 type: MT MCP 
  arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 17560 
  Speed: 898 MHz min/max: 800/2200 MHz Core speeds (MHz): 1: 898 2: 898 
  3: 898 4: 898 
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
  vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0116 
  Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) 
  v: 3.3 Mesa 20.2.6 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Dell 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 
  Sound Server: ALSA v: k5.4.0-77-generic 
Network:
  Device-1: Broadcom and subsidiaries BCM43142 802.11b/g/n 
  vendor: Dell Wireless 1704 802.11n + BT 4.0 driver: wl v: kernel 
  port: f040 bus ID: 07:00.0 chip ID: 14e4:4365 
  IF: wlan0 state: dormant mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Dell driver: r8169 v: kernel port: e000 bus ID: 09:00.0 
  chip ID: 10ec:8168 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 465.76 GiB used: 257.72 GiB (55.3%) 
  ID-1: /dev/sda vendor: Seagate model: ST500LM012 HN-M500MBB 
  size: 465.76 GiB speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> 
  rev: 0003 scheme: MBR 
Partition:
  ID-1: / size: 456.95 GiB used: 257.72 GiB (56.4%) fs: ext4 dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 76.0 C mobo: 60.0 C 
  Fan Speeds (RPM): cpu: 4769 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/anydesk-stable.list 
  1: deb http://deb.anydesk.com/ all main
  Active apt repos in: /etc/apt/sources.list.d/atareao-atareao-focal.list 
  1: deb http://ppa.launchpad.net/atareao/atareao/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
  1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/chrome-remote-desktop.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome-remote-desktop/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/deadsnakes-ppa-focal.list 
  1: deb http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/gezakovacs-ppa-focal.list 
  1: deb http://ppa.launchpad.net/gezakovacs/ppa/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
  No active apt repos in: /etc/apt/sources.list.d/metasploit-framework.list 
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyssa main upstream import backport
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/opera-stable.list 
  1: deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases)
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list 
  1: deb [signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/spotify.list 
  1: deb http://repository.spotify.com stable non-free
Info:
  Processes: 261 Uptime: 19m Memory: 5.68 GiB used: 2.45 GiB (43.1%) 
  Init: systemd v: 247 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.1.4 running in: gnome-terminal inxi: 3.0.38 

Code: Select all

rithik@rithik:~$ sudo ip link set wlan0 down
rithik@rithik:~$ sudo iw wlan0 set monitor control
command failed: Operation not supported (-95)

Code: Select all

rithik@rithik:~$ sudo airmon-ng
[sudo] password for rithik:     

PHY	Interface	Driver		Chipset

phy0	wlan0		wl		Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)

rithik@rithik:~$ sudo airmon-ng check kill

Killing these processes:

    PID Name
   1002 wpa_supplicant
   8204 avahi-daemon
   8208 avahi-daemon

rithik@rithik:~$ sudo airmon-ng start wlan0

Found 2 processes that could cause trouble.
Kill them using 'airmon-ng check kill' before putting
the card in monitor mode, they will interfere by changing channels
and sometimes putting the interface back in managed mode

    PID Name
   8221 avahi-daemon
   8222 avahi-daemon

PHY	Interface	Driver		Chipset

phy0	wlan0		wl		Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)

		(experimental wl monitor mode vif enabled for [phy0]wlan0 on [phy0]prism0)

rithik@rithik:~$ sudo airmon-ng check kill

Killing these processes:

    PID Name
   8437 avahi-daemon
   8444 avahi-daemon

rithik@rithik:~$ sudo airmon-ng start wlan0

Found 2 processes that could cause trouble.
Kill them using 'airmon-ng check kill' before putting
the card in monitor mode, they will interfere by changing channels
and sometimes putting the interface back in managed mode

    PID Name
   8458 avahi-daemon
   8459 avahi-daemon

PHY	Interface	Driver		Chipset

phy0	wlan0		wl		Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)

		(experimental wl monitor mode vif already enabled for [phy0]wlan0 on [phy0]prism0)

rithik@rithik:~$ sudo kill 8458
rithik@rithik:~$ sudo kill 8459
kill: (8459): No such process
rithik@rithik:~$ sudo airmon-ng check kill

Killing these processes:

    PID Name
   8653 avahi-daemon
   8660 avahi-daemon

rithik@rithik:~$ sudo airmon-ng start wlan0

Found 2 processes that could cause trouble.
Kill them using 'airmon-ng check kill' before putting
the card in monitor mode, they will interfere by changing channels
and sometimes putting the interface back in managed mode

    PID Name
   8673 avahi-daemon
   8674 avahi-daemon

PHY	Interface	Driver		Chipset

phy0	wlan0		wl		Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)

		(experimental wl monitor mode vif already enabled for [phy0]wlan0 on [phy0]prism0)

rithik@rithik:~$ sudo iwconfig
eth0      no wireless extensions.

prism0    no wireless extensions.

lo        no wireless extensions.

wlan0     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=200 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
rithik@rithik:~$ sudo systemctl start NetworkManager
rithik@rithik:~$ 

Code: Select all

rithik@rithik:~$ sudo ifconfig wlan0 down
[sudo] password for rithik:     
rithik@rithik:~$ sudo iwconfig wlan0 mode monitor
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Operation not supported

Code: Select all

rithik@rithik:~$ sudo systemctl stop NetworkManager
[sudo] password for rithik:     
rithik@rithik:~$ sudo iwconfig wlan0 mode monitor
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Operation not supported.
rithik@rithik:~$ sudo iwconfig wlan0 mode monitor
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Operation not supported

Code: Select all

sudo apt-get install b43-fwcutter firmware-b43-installer
[sudo] password for root:     
Reading package lists... Done
Building dependency tree       
Reading state information... Done
b43-fwcutter is already the newest version (1:019-4).
firmware-b43-installer is already the newest version (1:019-4).
0 upgraded, 0 newly installed, 0 to remove and 18 not upgraded

Code: Select all

pi@raspberrypi ~ $ sudo iwconfig wlan1 mode ad-hoc
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan1 ; Device or resource busy.

pi@raspberrypi ~ $ sudo iwconfig wlan0 mode ad-hoc
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Operation not supported.
pi@raspberrypi ~ $ 

Code: Select all

$ sudo iwconfig wlan0 mode Ad-Hoc
Error for wireless request "Set Mode" (8B06) : 
		SET failed on device wlan0 ; Device or resource busy