Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Sorry Guest, you are banned from posting and sending personal messages on this forum.

This ban is not set to expire.

[XXLRay]

I have a Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter on Ubuntu 12.04. It's a USB adpater in addition to my internal one. "sudo airmon-ng start wlan1" gives the following:

Code: [Select]

Found 7 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
616 avahi-daemon
622 avahi-daemon
924 NetworkManager
1128 wpa_supplicant
7576 dhclient
7962 dhclient
8158 dhclient
Process with PID 7885 (wlan1) is running on interface wlan1
Process with PID 8158 (dhclient) is running on interface wlan1
Process with PID 7962 (dhclient) is running on interface wlan0


Interface Chipset Driver

wlan1 Unknown r8712u (monitor mode enabled)
wlan0 Unknown iwlwifi - [phy0]
As you can see it says "monitor mode enabled" but there is no mon0 device. Is this because the chipset is not listed on the supported devices list?

[misterx]

Where is it written the chipset is not supported?

Is it a mac80211 driver or the manufacturer's driver?

Have you tested injection on that wlan1? Btw, kill those processes.

[XXLRay]

Where is it written the chipset is not supported?

I could just not find it explicitly written in the list of supported chipsets and it does not work as I expected it to.

Is it a mac80211 driver or the manufacturer's driver?

It's the driver which comes with Ubuntu 12.04

Have you tested injection on that wlan1?

No.

Btw, kill those processes.

Yes, I will do so if I have the rest running.

[misterx]

Well, the list of chipset change very often and it' not easy to keep up with them and all the different drivers that exist. So, a chipset that isn't marked as supported can work. Do the injection test.

So, I'll assume that's the manufacturer driver and in this case, it doesn't support monitor mode. Or you can try the injection test to see by yourself. And try wlan1 too.

You'll have to kill them or you'll have issues with other tools (including testing injection).

[XXLRay]

The processes pop up again automatically after I kill them and to the best of my knowledge they are quite essential for a network connection. Neither injection nor choosing wlan1 works:

Code: [Select]

$ sudo airmon-ng start wlan1


Found 6 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
6379 avahi-daemon
6380 avahi-daemon
6479 NetworkManager
6493 wpa_supplicant
6505 dhclient
6508 dhclient
Process with PID 5364 (wlan1) is running on interface wlan1
Process with PID 6508 (dhclient) is running on interface wlan1
Process with PID 6505 (dhclient) is running on interface wlan0


Interface Chipset Driver

wlan1 Unknown r8712u (monitor mode enabled)
wlan0 Unknown iwlwifi - [phy0]

Code: [Select]

$ sudo airodump-ng wlan1
ioctl(SIOCSIWMODE) failed: Invalid argument

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 wlan1 <#>'
Sysfs injection support was not found either.

Code: [Select]

$ sudo aireplay-ng -9 wlan1
ioctl(SIOCSIWMODE) failed: Invalid argument

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 wlan1 <#>'
Sysfs injection support was not found either.
(I find the verification questions quite hard to answer by the way - took me quite some time of research)

[misterx]

You probably have an old version of aircrack-ng, please update it.

And give a try to wlan0, iwlwifi should work fine.

[XXLRay]

I put the USB WLAN adapter into another PC and installed aircrack-ng 1.2.beta1. When I enter "sudo airmon-ng start wlan0" the device is not listed at all although ifconfig shows it and I can see the networks using Ubuntu's network tool.

[thefluffynaruto]

Hey, did you ever get this fixed? I'm having the exact same problem, even the same driver but a slightly different card.

[XXLRay]

No, it's not solved yet and I am still hoping for an answer.

[pimpcode74]

try putting wlan1 in monitor mode manually
instead of running airmon-ng

# ifconfig wlan1 down
# iw dev wlan1 interface add mon0 type monitor
# ifconfig wlan1 up
 
$ sudo airodump-ng mon0

if you are able to see APs try injection test, if it works, you're good to go

if mon0 doesnt work, you might try using wlan1 interface directly instead of mon0

# ifconfig wlan1 down
# iwconfig wlan1 mode monitor
# ifconfig wlan1 up

$ sudo airodump-ng wlan1

[XXLRay]

Note that it's wlan0 in my other computer now.

Unfortunately I got an error message on the methods you proposed:

Code: [Select]

sudo ifconfig wlan0 down
sudo iw dev wlan0 interface add mon0 type monitor
nl80211 not found.

Code: [Select]

sudo ifconfig wlan0 down
sudo iw dev wlan0 mode monitor
nl80211 not found.

[pimpcode74]

do you have the cfg80211 module installed?
 
lmsod | grep cfg80211

if not:
modprobe cfg80211

if you don't have cfg80211 module you need to compile it and load it,
then you should be able to get into monitor mode. you may also try getting the latest
version of the driver for your device in addition to cfg80211.

[XXLRay]

It was not installed but after "sudo modprobe cfg8021" the command "sudo airmon-ng start wlan0" does not list wlan0 (no interface at all). The error message when setting monitor mode is now different:

Code: [Select]

sudo ifconfig wlan0 down
sudo iw dev wlan0 interface add mon0 type monitor
command failed: No such device (-19)
But wlan0 is listed on iwconfig.

[pimpcode74]

Could you please paste a copy of the output of lsmod

[misterx]

And the end of dmesg right after that command.