-
Перейти на CTF площадку Игры Кодебай
Выполняйте задания по кибербезопасности в формате CTF и получайте бесценный опыт. Ознакомиться с подробным описанием можно тут.
-
B правой части каждого сообщения есть стрелки ⇧ и ⇩. Не стесняйтесь оценивать ответы. Чтобы автору вопроса закрыть свой тикет, надо выбрать лучший ответ. Просто нажмите значок ✔ в правой части сообщения.
roooooot
-
#1
Купил данный девайс, kali его видит, подключиться к домашней сети даёт. Однако брал я сию вещь для режима мониторинга. Через airmon-ng отображается, однако после ввода airmon-ng start wlan0 ничегошеньки не меняется. Через команду iwconfig wlan0 mode monitor выбивает
Error for wireless request «Set Mode» (8B06) :
SET failed on device wlan0 ; Invalid argument.
Я решил что всё дело в драйверах, однако на офф сайте версия только для Kernel 2.6.18~3.19.3, а у меня как раз таки 4.19.0 , и что делать в данном случае понятия не имею. Попробовать поставить эти дрова попробовал, но кроме десятка ошибок ничего не добился. Подскажите, если кто сталкивался, есть ли вариант всё сделать «что бы работало», или легче просто другую балалайку купить?
-
#2
Купил данный девайс, kali его видит, подключиться к домашней сети даёт. Однако брал я сию вещь для режима мониторинга. Через airmon-ng отображается, однако после ввода airmon-ng start wlan0 ничегошеньки не меняется. Через команду iwconfig wlan0 mode monitor выбивает
Error for wireless request «Set Mode» (8B06) :
SET failed on device wlan0 ; Invalid argument.
Я решил что всё дело в драйверах, однако на офф сайте версия только для Kernel 2.6.18~3.19.3, а у меня как раз таки 4.19.0 , и что делать в данном случае понятия не имею. Попробовать поставить эти дрова попробовал, но кроме десятка ошибок ничего не добился. Подскажите, если кто сталкивался, есть ли вариант всё сделать «что бы работало», или легче просто другую балалайку купить?
TP Link TL-WN722N monitor mode IS WORK!
Спешу сообщить всем тем кто приобрел себе этот замечательный девайс для тестирования на проникновение беспроводных сетей, замечательнейшую новость
codeby.net
roooooot
-
#3
TP Link TL-WN722N monitor mode IS WORK!
Спешу сообщить всем тем кто приобрел себе этот замечательный девайс для тестирования на проникновение беспроводных сетей, замечательнейшую новость
codeby.net
-
Снимок экрана от 2019-08-12 20-59-37.png
113 КБ
· Просмотры: 998
roooooot
-
#5
При установке драйвера ошибок не было, но ничего так и не заработало… После ввода
aireplay-ng —test wlan0
выдало
Код:
ioctl(SIOCSIWMODE) failed: Invalid argument
ioctl(SIOCSIWMODE) failed: Invalid argument
Error setting monitor mode on wlan0
-
#6
При установке драйвера ошибок не было, но ничего так и не заработало… После ввода
aireplay-ng —test wlan0
выдалоКод:
ioctl(SIOCSIWMODE) failed: Invalid argument ioctl(SIOCSIWMODE) failed: Invalid argument Error setting monitor mode on wlan0
Может быть
iwconfig wlan0 mode auto
aireplay-ng — — test wlan0
И да убедись что это именно wlan0
roooooot
-
#7
Может быть
iwconfig wlan0 mode auto
aireplay-ng — — test wlan0
И да убедись что это именно wlan0
Код:
root@kali:~# iwconfig
wlan0 unassociated ESSID:"" Nickname:"<WIFI@REALTEK>"
Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
lo no wireless extensions.
eth1 no wireless extensions.
eth0 no wireless extensions.
root@kali:~# iwconfig wlan0 mode auto
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Operation not permitted.
root@kali:~# aireplay-ng --test wlan0
ioctl(SIOCSIWMODE) failed: Operation not permitted
ioctl(SIOCSIWMODE) failed: Operation not permitted
Error setting monitor mode on wlan0
-
#8
Код:
root@kali:~# iwconfig wlan0 unassociated ESSID:"" Nickname:"<WIFI@REALTEK>" Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 lo no wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. root@kali:~# iwconfig wlan0 mode auto Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Operation not permitted. root@kali:~# aireplay-ng --test wlan0 ioctl(SIOCSIWMODE) failed: Operation not permitted ioctl(SIOCSIWMODE) failed: Operation not permitted Error setting monitor mode on wlan0
su -i или su -l или перед каждой командой sudo
ifconfig wlan0 down
iwconfig wlan0 mode auto
ifconfig wlan0 up
roooooot
-
#9
su -i или su -l или перед каждой командой sudo
ifconfig wlan0 down
iwconfig wlan0 mode auto
ifconfig wlan0 up
Всё повторяется, одна и та же ошибка. Буду короче менять это шило на другое мыло, авось повезёт… Спасибо за помощь!
-
#10
Всё повторяется, одна и та же ошибка. Буду короче менять это шило на другое мыло, авось повезёт… Спасибо за помощь!
Так operation not permitted это всего лишь ошибка о том что у вас недостаточно прав (вы не root)
Без sudo, даже альфу в monitore Mode не переведёшь
roooooot
-
#11
Так operation not permitted это всего лишь ошибка о том что у вас недостаточно прав (вы не root)
Без sudo, даже альфу в monitore Mode не переведёшь
Вчера попробовал, теперь другую ошибку выдало. Так что решил не заморачиваться и купить wn727n. Спасибо за советы
-
#12
Доброго времени суток, наткнулся на такой же баян по поводу tl-wn722n v3 всё что написали в теме сделал но ошибка та же error setting monitor mode on wlan0 есть ли у вас решение данной проблемы?
f22
Codeby Team
-
#14
Из первого поста я понял что с 2018 года эту проблему так и не решили и нету смысла пытаться что либо делать т.к этот адаптер не пригоден для вардрайвинга из под Линукс?
f22
Codeby Team
-
#15
Из первого поста я понял что с 2018 года эту проблему так и не решили и нету смысла пытаться что либо делать т.к этот адаптер не пригоден для вардрайвинга из под Линукс?
Первая версия этого адаптера на kali работает норм.
-
#16
Первая версия этого адаптера на kali работает норм.
Щас пробую через кали 2019.2 установить драйвера и завести шарманку
P.s. может кто оставить ссылку на норм альфу с али, говоря норм альфу я подразумеваю не лютую подделку, а подделку которая на норм чипсете и норм чувствительная.
Щас пробую через кали 2019.2 установить драйвера и завести шарманку
P.s. может кто оставить ссылку на норм альфу с али, говоря норм альфу я подразумеваю не лютую подделку, а подделку которая на норм чипсете и норм чувствительная.
Последнее редактирование: 13.01.2020
-
#17
Попробуй самый простой способ программа airgeddon она покажет поддерживает твой модем режим мониторинга или нет
- Печать
Страницы: [1] 2 Все Вниз
Тема: Wifi ad-hoc не поддерживается (Прочитано 7751 раз)
0 Пользователей и 1 Гость просматривают эту тему.

romeg
Ноутбук Acer Extensa 5620, ubuntu 8.04, установка с нуля.
Драйвер карты Wifi — из коробки, открытый.
В networkManager отключаю режим роуминга, в /etc/network/interfaces прописываю wireless-mode ad-hoc.
В данный режим устройство не входит, команда iwconfig все равно говорит, что режим — Managed
При рестарте сети выдает ошибку, что неверное значение режима.
Когда на компе был ubuntu 7.10 — все работало из коробки. При этом драйвер Wifi карточки стоял преприоретарный.
Это потому что драйвер в 8.04 не поддерживает режим ad-hoc?
Как решить проблему? Только перестановкой драйвера?
Если да, то как вручную заменить установленный драйвер на старый препреоретарный драйвер?
Если нет, то где копать?

12d3
а слабо сказать, какая вайфай карта?
ЗЫ [оффтоп] : выучите уже блин все это слово — проприетарный =)

romeg
Вот такая карта:
Встроенный адаптер беспроводной сети: Intel® PRO/Wireless 3945ABG (802.11a/b/g)

12d3
sudo ifdown wlan0 && sudo iwconfig wlan0 mode ad-hoc && sudo ifup wlan0

romeg
Вот какой ответ получил:
Error for wireless request «Set Mode» (8B06) :
SET failed on device wlan0 ; Invalid argument.
Когда делаю рестарт сети — аналогичная ошибка возникает, а wlan0 остается в режиме «Managed»
Значит, открытый драйвер из коробки не поддерживает режим ad-hoc?

teop
Так, а что там по ifconfig выдает?

12d3
раз у меня на такой-же карточке работает, то и у вас должно.
а если вместо ifdown wlan0 сделать ifconfig wlan0 down, и с ifup аналогично.

romeg
спасибо, получилось.
Командой
sudo ifconfig wlan0 down && sudo iwconfig wlan0 mode ad-hoc && sudo ifconfig wlan0 up
сеть поднялась, iwconfig показывает режим ad-hoc, но все работает до следующей перезагрузки.
После перезагрузки — снова wlan0 отключена, режим Managed, пока не сделаешь вышеуказанную команду.
Как можно сделать так, чтобы wlan0 работал по умолчанию?
Ниже пишу, что у меня сейчас в /etc/network/interfaces
====
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
auto wlan0
iface wlan0 inet static
address 192.168.0.1
netmask 255.255.255.0
broadcast 192.168.0.255
wireless-key 1234567890
wireless-essid pantera
wireless-mode ad-hoc
#wireless-channel 1
====

DJArty
Возможно еще NetworkManager следует тушить, а Wlan поднимать руками или скриптом (гдето в моём посте было)

Oleg
сеть поднялась, iwconfig показывает режим ad-hoc, но все работает до следующей перезагрузки.
После перезагрузки — снова wlan0 отключена, режим Managed, пока не сделаешь вышеуказанную команду.
Смотреть сюда.

romeg
Вставка в /etc/rc.local строк
sleep 15s
/etc/init.d/networking restart
не помогла, так как в моем случае команда sudo /etc/init.d/networking restart сеть не поднимала сама по себе (не знаю почему, пишет Error for wireless request «Set Mode» (8B06) : SET failed on device wlan0 ; Invalid argument).
Но проблема решилась, когда я в rc.local вставил следующую строку:
ifconfig wlan0 down && iwconfig wlan0 mode ad-hoc && ifconfig wlan0 up
все заработало.
Видимо, это единственное решение, хотя, как я думаю, не очень красивое.
Спасибо 12d3 и Oleg — совместными усилиями помогли.

romeg
При перезагрузке теперь все работает.
А после выхода ис спящего режима — нет, снова вручную приходится включать.
Как заставить wlan0 подниматься после выхода из спящего режима?
Может в какой-то скрипт засунуть перезапуск, подобно /etc/rc.local ?

kosilas
Помогите поднять ad-hoс на карте BCM4318 (wl-138g)
Драйвера ставил b43-fwcutter
При команде
ifconfig wlan0 down && iwconfig wlan0 mode ad-hoc && ifconfig wlan0 upпишет:
Error for wireless request "Set Mode" (8B06) :Interface такой:
SET failed on device wlan0 ; Operation not permitted.
auto loВ чем трабл? Кривые дрова ?
iface lo inet loopback
auto eth0
iface eth0 inet static
adress 192.168.1.6
#network 192.168.0.0
netmask 255.255.255.0
#broadcast 192.168.0.255
gateway 192.168.1.2
up route add default gw 192.168.1.2 eth0
auto wlan0
iface wlan0 inet static
address 192.168.0.12
netmask 255.255.255.0
wireless-essid homenet

romeg
видимо у тебя прав root нет.
Проделывай те же команды через sudo:
sudo ifconfig wlan0 down && iwconfig wlan0 mode ad-hoc && ifconfig wlan0 up

kosilas
- Печать
Страницы: [1] 2 Все Вверх
Hi all,
I’m trying to setup my Toshiba laptop to connect to a wireless network at work (luckily I can hijack a wired connection for the time being until I set it up). I’m fairly new to linux, so I’m not really sure where to start. I read the wiki on setting up wireless and have googled for a while, but have yet to find a definitive method to set it up. I’ve installed (thanks to the awesomeness of pacman) wireless_tools, wlan-ng26, and pcmcia-cs. I have also determined from some other forums that my wireless card should run off the orinoco_cs driver (I enabled that module in my rc.conf). When I type the command, iwconfig, i get…
lo no wireless extensions.
sit0 no wireless extensions.
eth0 no wireless extensions.
… I’ve tried editing my rc.conf and conf.d/wireless as I’ve seen suggested on this and other forums, but when I try to start the network with my wlan0 entry, I get the message,
«Error for wireless request
«Set Mode» (8B06) :
SET failed on device eth0 ; Operation not supported.»
Here is my rc.conf file (excuse its messiness, I have a static IP at home, but must use DHCP here at work, so I just comment/uncomment to switch between the two)…
#
# /etc/rc.conf — Main Configuration for Arch Linux
#
#
# Localization
#
# HARDWARECLOCK: set to «UTC» or «localtime»
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/unimaps
# USECOLOR: use ANSI color sequences in startup messages
#
HARDWARECLOCK=»localtime»
TIMEZONE=Canada/Pacific
KEYMAP=us
CONSOLEFONT=
CONSOLEMAP=
USECOLOR=»yes»
# Scan for LVM volume groups at startup, required if you use LVM
USELVM=»no»
#
# Networking
#
HOSTNAME=»myhost»
#
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
#
MODULES=(!usbserial !ide-scsi orinoco_cs)
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# (prefix an interface in INTERFACES with a ! to disable it)
#
# Note: to use DHCP, set your interface to be «dhcp» (eth0=»dhcp»)
#
lo=»lo 127.0.0.1″
#######eth0=»eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255″
eth0=»dhcp»
wlan0=»dhcp»
########eth0=»eth0 192.168.1.105 netmask 255.255.255.0 broadcast 192.168.1.255″
INTERFACES=(lo eth0 wlan0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
#
gateway=»default gw 192.168.1.1″
#########ROUTES=(gateway)
ROUTES=(!gateway)
#
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
# (prefix a daemon with a @ to start it up in the background)
#
DAEMONS=(syslog-ng hotplug pcmcia network netfs crond alsa fnfxd acpid)
# End of file
And here is my conf.d/wireless file…
#
# Settings for wireless cards
#
# For each wireless interface declared in INTERFACES (in rc.conf), declare
# a wlan_${IF} variable that contains the arguments to be passed to
# iwconfig(8). Then list the original interface name in the
# WLAN_INTERFACES array.
#
wlan_wlan0=»eth0 mode managed essid default»
WLAN_INTERFACES=(wlan0)
I would have posted this in the networking forum if I had more of a clue what I’m talking about. Any help/direction would be greatly appreciated.
Thanks,
-Scott
I’ve followed this tutorial on installing aircrack on Ubuntu 14.04:
https://www.youtube.com/watch?v=xdvGZlUzfRs&src_vid=OF0UjeoTXoI&feature=iv&annotation_id=annotation_1882595149
I had to tweak a few things to get it to download successfully, but here is what I’m having issues with (and what I can’t find a solution for):
This command:
sudo airodump-ng mon0
of which I get the error:
Interface mon0:
ioctl(SIOCGIFINDEX) failed: No such device
The command iwconfig shows:
eth0 no wireless extensions.
lo no wireless extensions.
wlan0 IEEE 802.11abg ESSID:"nameofmynetwork"
Mode:Managed Frequency:5.765 GHz Access Point: 05:B1:51:42:A1:5D
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:on
Regarding mon0, what is it? I tried some solutions, such as killing processes and updating to the latest aircrack, but I still receive an error.
Any help is appreciated!
asked Nov 13, 2014 at 4:02
2
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
GewureGewure
3633 silver badges10 bronze badges
2
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:
-
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 doiwconfig. This is the command that you probably didn’t execute. If you did run it but you can’t seemon0afterwards, let us know what was the command’s output.
- 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
-
sudo airodump-ng <options> mon0- This starts capturing packets.
-
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.
-
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
Alaa AliAlaa Ali
30.5k11 gold badges93 silver badges105 bronze badges
3
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.
answered Feb 7, 2016 at 8:36
1
From what i’ve seen, in the latest ubuntu version (15.10) there is a problem when enabling monitor mode on mon0.
To do it clean and clear, use this command to kill any process that can cause problems sudo airmon-ng check kill , then use this command to enable monitor mode on mon0 sudo airmon-ng start wlan0 .
Now you can use mon0 with other *-ng commands.
answered Jan 6, 2016 at 17:24
SidahmedSidahmed
1,0462 gold badges14 silver badges27 bronze badges
Okay, first of all let’s start with killing all processes with sudo airmon-ng check kill , then enabling monitor mode with sudo airmon-ng start wlan0 , now the answer to your question is in the output of this command. Notice that it says in the bottom (experimental wl monitor mode vif enabled for [phy0]wlan0 on [phy0]prism0) for me it says prism0 this is the interface that was created for me when I used the airmon-ng start wlan0 command which is in general called mon0 but it’s not always the same so you need to check the name of the one that was created for you and use it in the next command. For example in my case, to start capturing packets I will type airodump-ng prism0 not mon0. I hope this answers your question.
answered Sep 18, 2016 at 20:33
if airodump-ng mon0 doesnt works for you;
give the previous one command as; «airmon-ng start wlp3s0» rather than «airmon-ng start wlan0» because wlan0 works for network on lan and wlp3s0 works for wireless network and then insert command «airodump-ng mon0»
this will surely work for you too
answered Dec 30, 2017 at 5:21
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
deathstroke
- Level 1
- Posts: 11
- Joined: Fri Jul 02, 2021 1:42 am
Monitor Mode Error
Error for wireless request «Set Mode» (8B06) :
SET failed on device wlan0 ; Operation not supported
Are there any solutions for this? Does this mean my wireless card doesnt support monitor mode? or Should I Install a different driver?
I’m a beginner in Linux, Somebody please help me out
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
SMG
- Level 24
- Posts: 20938
- Joined: Sun Jul 26, 2020 6:15 pm
- Location: USA
Re: Monitor Mode Error
Post
by SMG » Sat Jul 03, 2021 12:33 pm
deathstroke wrote: ↑
Sat Jul 03, 2021 12:25 am
I need a solution
Someone please answer!
Welcome to the forum, deathstroke.
Had you read Section 5 of READ: How To Get Help! you would have known to supply information about your hardware in order for us to be able to help you.
I do not know exactly what you are trying to accomplish, but I ran a search on the command you ran and found this Three ways to set wireless interface to Monitor mode and Managed mode. Maybe that will help.
If not, please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code markers and paste the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.
________________________________________
Edited to add:
3 Ways to put your Wi-Fi Interface in Monitor Mode in Linux which seems like it might be specific for Kali Linux, but it does list supported chipsets (hardware).
How to Put WiFi Interface into Monitor Mode in Linux? is dated for only a couple of months ago.
A woman typing on a laptop with LM20.3 Cinnamon.
-
deathstroke
- Level 1
- Posts: 11
- Joined: Fri Jul 02, 2021 1:42 am
Re: Monitor Mode Error
Post
by deathstroke » Sun Jul 04, 2021 2:48 am
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
Here you go. I’ll refer the other links you attached and I’ll let you know.
-
deathstroke
- Level 1
- Posts: 11
- Joined: Fri Jul 02, 2021 1:42 am
Re: Monitor Mode Error
Post
by deathstroke » Sun Jul 04, 2021 3:02 am
Based on the links you sent I tried these and here are the results
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
Doesn’t my wireless card support monitor mode?
-
SMG
- Level 24
- Posts: 20938
- Joined: Sun Jul 26, 2020 6:15 pm
- Location: USA
Re: Monitor Mode Error
Post
by SMG » Sun Jul 04, 2021 10:59 am
Your network info is showing the wireless as dormant. I am not familiar with that setting. Normally, the state is either up or down. Your Ethernet is showing as up.
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>
I did find this old thread BCM43142 monitor mode : operation not suported! which has the exact same wireless device. It seems to indicate the Linux drivers available for the card do not support monitor mode. I do not know if there is newer information or other information which might have a way for it to work.
A woman typing on a laptop with LM20.3 Cinnamon.
-
deathstroke
- Level 1
- Posts: 11
- Joined: Fri Jul 02, 2021 1:42 am
Re: Monitor Mode Error
Post
by deathstroke » Mon Jul 05, 2021 1:58 am
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
The threads suggest that I can work in a new interface called prism0 and not mon0
But how do set my card to that mode?
-
SMG
- Level 24
- Posts: 20938
- Joined: Sun Jul 26, 2020 6:15 pm
- Location: USA
Re: Monitor Mode Error
Post
by SMG » Mon Jul 05, 2021 11:34 am
deathstroke wrote: ↑
Mon Jul 05, 2021 1:58 am
The threads suggest that I can work in a new interface called prism0 and not mon0
But how do set my card to that mode?
What thread? I supplied quite a few links.
I do not have a computer with the same wireless card you have, so my ability to help you is limited.
I am going to return to my comment about your wireless connection being dormant. I found this explanation What does mean DORMANT mode in ip link show wlan0? which seems to indicate to me that you have to get the wireless in an up state before it is going to do anything for you.
A woman typing on a laptop with LM20.3 Cinnamon.
In this tutorial we’ll enable monitor mode on a TP-LINK TL-WN722N V2/V3 wireless adapter, on a Kali Linux machine running on VMware or VirtualBox.
Some sources may be confusing, and lead you to believe that you can only enable monitor mode on TP-LINK TL-WN722N v1 because it has one of the required chipsets for monitor mode, Atheros AR9271, and that you can’t enable it on V2/V3. You can, however.
To start off, if you’re using a virtual machine, first you’ll have to connect your wireless adapter to your Kali Linux virtual machine.
Set up the Adapter
Next, we’ll run some commands to set up the adapter.
First update and upgrade your package index.
sudo apt update && sudo apt upgrade
Reboot your machine.
sudo reboot
Install Linux headers for your Kali Linux.
sudo apt install linux-headers-$(uname -r)
Run the following commands to install the bc package and remote the r8188eu.ko module.
sudo apt install bc
sudo rmmod r8188eu.ko
Clone the Realtek driver from the aircrack-ng Github repository.
git clone https://github.com/aircrack-ng/rtl8188eus
Run the following commands.
cd rtl8188eus
sudo -i
echo "blacklist r8188eu" > "/etc/modprobe.d/realtek.conf"
exit
reboot
After the reboot run the following commands (we have to cd back into the rtl8188eus directory that we cloned earlier):
cd rtl8188eus
make
sudo make install
sudo modprobe 8188eu
To enable monitor mode, run the following commands:
sudo ifconfig wlan0 down
sudo airmon-ng check kill
sudo iwconfig wlan0 mode monitor
sudo ifconfig wlan0 up
sudo iwconfig
Here’s the output you should be seeing. You can see that the adapter is set to Mode: Monitor.
Troubleshooting When Enabling Monitor Mode
In some cases it doesn’t work right away. For example you may get the error Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Operation not permitted.
The solution that has worked for me every time is the following (credit to this Github user’s comment).
Run the following commands in this order:
sudo ifconfig wlan0 up
sudo rmmod r8188eu.ko
sudo modprobe 8188eu
sudo iwconfig wlan0 mode auto
sudo ifconfig wlan0 down
sudo iwconfig wlan0 mode monitor
sudo ifconfig wlan0 up
Now when you check iwconfig you should see the adapter is in monitor mode.
Conclusion
In this tutorial we set up a TP-LINK TL-WN722N V2/V3 adapter to run in monitor mode. If you have any issues or questions then please don’t hesitate to leave a comment. Hope this helped. Thank you.







