Airodump-ng is one of favorite tools in hacking wireless network. When I upgrade my ubuntu from Gutsy to Intrepid, I can’t run this application anymore. It’s not application error because I can run it in Gutsy version before. My wireless card chip set is ‘ipw3945’.
The error message is a bit complicated as you see below.
_________________________________________
ioctl(SIOCSIWMODE) failed: Device or resource busy
ARP linktype is set to 1 (Ethernet) – expected ARPHRD_IEEE80211,
ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead. Make
sure RFMON is enabled: run ‘airmon-ng start wlan0 <#>’
Sysfs injection support was not found either.
_________________________________________
Mean that if you want your airodump-ng run, you will need to try to fix the bolds problems above. Your problem may be one of it but in my case not even one of the error message.
Try to figure out the answer quite some times which is actually is very simple.
It’s only change the ipw3945 chip set mode from ‘Managed‘ to ‘monitor‘.
Step 1. Check your chip set mode
From the Terminal Screen, type ‘iwconfig wlan0‘. Your wireless card name (wlan0) may be different. It will depend on your wireless card chip set or your Ubuntu version. When I used Gutsy or lower version, my wireless card (ipw3945) is ‘eth1’ but when I upgrade to ‘Intrepid’, it become ‘wlan0’.
If you don’t remember the iwconfig command line, just type ‘iwconfig –help‘.
What we need now is the information in ‘interface mode’. We have to change the ‘mode’ from ‘Managed‘ to ‘monitor‘.
Step 2. Change the wireless card mode.
First turn of your wireless card. Type ‘sudo ifconfig wlan0 down‘.
Second, change your wireless card mode from ‘Managed’ to monitor. Type ‘sudo iwconfig wlan0 mode monitor‘.
Third, turn on again your wireless card. Type ‘sudo ifconfig wlan0 up‘.
Fourth, check the wireless card status. Type ‘sudo iwconfig wlan0‘.
Now, my wireless card mode is ‘monitor‘ and you are ready to run ‘airdump-ng’ application again.
Thx for you post. It was very useful. However, I’m using a ASUS WL-167g v2 and when i’m monitoring it finds only networks using WAP. Is it normal or maybe it came with a configuration created only to find this encryptions?
Thank you.
Thanks for the post really helpful for me.
Thanks a lot. That’s really helped me.
Thank you, exactly what I was looking for.
Thanks dude this really Helped me alot.
Thanks a lot. That’s really helped me.
hey it still gives an error for me.
please help.
the error is
iwconfig eth1 mode Monitor
Error for wireless request “Set Mode” (8B06) :
SET failed on device eth1 ; Invalid argument.
what should i do.
please reply as soon as possible.
You are great ! 🙂 Thx a lot!
/Marcin from Poland
did you forget to put down the interface before attempting to change the mode
Thanks! Worked perfectly on my Lucid Lynx (Acer Aspire laptop) box.
nice… worked on BT5 🙂
Superb!!!! Thanx a lot!
There is a problem.
Error: Capability not found
Error: Capability not found
Error: Capability not found
Error: Capability not found
Everytime I type your commands !
What is going on here?
Very Helpful. One thing i ran into was the auto reconnect problem that would not let me switch it to monitor mode when i turned it off. So you will have to disconnect from the internet on the wireless card you are trying to use then you will be able to set it up in monitor mode. Thanks every one for the help
Error for wireless request “Set Mode” (8B06) :
SET failed on device eth1 ; Invalid argument
sweet. works on BT5_r1!
note to newbies: this kicks you off all wifi.
so if you are training online, you might want to copy the respective steps of your training.
its really helpful …
thnx
ty dude rock on its very helpfull for me
Still getting this:
Error for wireless request “Set Mode” (8B06) :
SET failed on device eth1 ; Invalid argument
I’ve searched for hours and tried everything I know and… nothing.
Any suggestion or advice would be greatly appreciated. 🙂
winner winner chicken dinner!
The only problem I had was after getting it to work in monitor mode I couldn’t get it to work back in “managed” mode. It would connect and seem to be working but I couldn’t hit my gateway. I simply reversed operation but required a reboot to get back on the internet to find a solution….still looking.
Hello my friend it still give me an error can you please help me … i been try to figure this out for about 1 months now
hey it still gives an error for me.
please help.
the error is
iwconfig eth1 mode Monitor
Error for wireless request “Set Mode” (8B06) :
SET failed on device eth1 ; Invalid argument.
what should i do.
please reply as soon as possible
hi, this a very usefull trick, thanks for that, anyway, i’m still having this issue with airodump, it doesn’t show any signal, i mean “nothing” they told me that i should use “sudo airmon-ng check kill” but the thing still happening.
any advice?
thanks for this post.
just a note, i have to switch back to managed mode if i want to actually connect to a network.
sudo iwconfig eth1 mode monitor:
Error for wireless request “Set Mode” (8B06) :
SET failed on device eth1 ; Invalid argument.
Here is a short solution for you guys :
With some drivers, you need to bring the interface down first:
sudo ifconfig wlan0 down
sudo iwconfig wlan0 mode managed
sudo ifconfig wlan0 up
Works like a charm! 😉
Change the second line I wrote to monitor mode…
RP
thannx a lot for post. It is so useful.
plzzzz wlan0 IEEE 80.2.11LLabgn mode monitor frament thr:off power management:on
please help me??
while changing mode to monitor it gives me error:
prompt$sudo iwconfig eth1 mode monitor
Error for wireless request “Set Mode” (8B06) :
SET failed on device eth1 ; Invalid argument.
i’m using backbox
and while running following command:
prompt$ sudo airmon-ng start eth1
Found 4 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
6760 wpa_supplicant
7987 NetworkManager
8004 avahi-daemon
8005 avahi-daemon
Interface Chipset Driver
eth1 Unknown wl (monitor mode enabled)
and after that i did kill all of these processes with “kill -9 PID”, but it restarts these processes again…… any solution??
Had the same problem, fix worked great. Thanks
hi thank for the post after putting it in monitor mode like shown above i still can see any interfaces plz can u help me?????????????
Thanks , its working , nice post
This is the only thing that worked from all the things I tried. Thank you, thank you:)
Thanks, great post. Also useful for backtrack users.
sudo iwconfig eth1 mode monitor
Error for wireless request “Set Mode” (8B06) :
SET failed on device eth1 ; Operation not supported.
plzzzzzzzzzzzzzzzzzzzz help
Thanks! That helped a lot!
@ samer and for those who fail to set ETH interface eg. ETH1 or ETH2 …..correct me if im wrong but its only for setting wireless adapters to moniter mode
you cant use the aircrack suit with an ethernet adapter
…also to stop moniter mode its
#airmon-ng stop
Thank you so much for this tutorial, fixed my problem! 🙂
Thanks for the help!
thanks a lot
it fix my problem
thx you so much very helpful
Very useful, I was stomped for a moment but post resolved the problem
very so good. thank a lot. you are my god. thank u
thank you, it’s really helpfull
thanks a lot
not working for me please help
whenever i try it shows this
“Error for wireless request “Set Mode” (8B06) :
SET failed on device wlp2s0 ; Operation not supported.”
I try to Step2. but i see this problem
‘sudo ifconfig wlan0 down‘. -done
‘sudo iwconfig wlan0 mode monitor‘.
–> SET failed on device wds0 ; Operation not supported.
What is mean, not supporteed??
if anyone reply me, i can show my process log file