Aircrack-ng forum
General Category => General help => Topic started by: XXLRay on June 11, 2013, 07:40:52 am
-
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:
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?
-
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.
-
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.
-
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).
-
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:
$ 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]
$ 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.
$ 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)
-
You probably have an old version of aircrack-ng, please update it.
And give a try to wlan0, iwlwifi should work fine.
-
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.
-
Hey, did you ever get this fixed? I'm having the exact same problem, even the same driver but a slightly different card.
-
No, it's not solved yet and I am still hoping for an answer.
-
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
-
Note that it's wlan0 in my other computer now.
Unfortunately I got an error message on the methods you proposed:
sudo ifconfig wlan0 down
sudo iw dev wlan0 interface add mon0 type monitor
nl80211 not found.
sudo ifconfig wlan0 down
sudo iw dev wlan0 mode monitor
nl80211 not found.
-
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.
-
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:
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.
-
Could you please paste a copy of the output of lsmod
-
And the end of dmesg right after that command.
-
Hey guys, have the exact same usb with the exact same problem:
Here is an 'lsmod' output:
Module Size Used by
fuse 62706 5
binfmt_misc 12958 1
loop 22955 0
dm_crypt 18373 0
joydev 17318 0
hid_logitech_dj 17355 0
hid_generic 12386 0
r8712u 143090 0
usbhid 40793 1 hid_logitech_dj
hid 81617 3 hid_generic,usbhid,hid_logitech_dj
radeon 729740 2
ttm 62521 1 radeon
drm_kms_helper 27236 1 radeon
drm 202248 3 ttm,drm_kms_helper,radeon
snd_hda_codec_hdmi 31480 1
iTCO_wdt 12832 0
iTCO_vendor_support 12705 1 iTCO_wdt
eeepc_wmi 12601 0
i2c_algo_bit 12842 1 radeon
coretemp 12855 0
i2c_i801 17046 0
kvm_intel 118161 0
mei 31840 0
i2c_core 24042 5 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,radeon
asus_wmi 18804 1 eeepc_wmi
lpc_ich 16758 0
sparse_keymap 12761 1 asus_wmi
rfkill 19167 3 asus_wmi
acpi_cpufreq 13355 1
mperf 12454 1 acpi_cpufreq
mfd_core 12602 1 lpc_ich
snd_hda_codec_realtek 55447 1
snd_hda_intel 30803 5
processor 28456 1 acpi_cpufreq
snd_hda_codec 88216 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep 13190 1 snd_hda_codec
snd_pcm 68524 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 13019 2 snd_pcm,snd_hda_intel
psmouse 69191 0
evdev 17651 6
serio_raw 12941 0
video 17687 1 asus_wmi
kvm 309830 1 kvm_intel
thermal_sys 22342 2 video,processor
wmi 13244 1 asus_wmi
snd_timer 22813 1 snd_pcm
snd 53078 17 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 13027 1 snd
button 12945 0
ext4 371544 1
crc16 12344 1 ext4
jbd2 71913 1 ext4
mbcache 13115 1 ext4
dm_mod 63778 1 dm_crypt
usb_storage 48070 2
sg 26096 0
sd_mod 40550 7
crc_t10dif 12349 1 sd_mod
crc32c_intel 12748 0
ghash_clmulni_intel 13063 0
aesni_intel 50747 0
aes_x86_64 16844 1 aesni_intel
ablk_helper 12573 1 aesni_intel
cryptd 14561 3 ghash_clmulni_intel,aesni_intel,ablk_helper
xts 12723 1 aesni_intel
lrw 12872 1 aesni_intel
gf128mul 13048 2 lrw,xts
microcode 30457 0
xhci_hcd 78154 0
ahci 25061 2
libahci 22919 1 ahci
libata 141636 2 ahci,libahci
ehci_hcd 40532 0
scsi_mod 162399 4 sg,usb_storage,libata,sd_mod
usbcore 134001 5 usb_storage,ehci_hcd,r871Module Size Used by
fuse 62706 5
binfmt_misc 12958 1
loop 22955 0
dm_crypt 18373 0
joydev 17318 0
hid_logitech_dj 17355 0
hid_generic 12386 0
r8712u 143090 0
usbhid 40793 1 hid_logitech_dj
hid 81617 3 hid_generic,usbhid,hid_logitech_dj
radeon 729740 2
ttm 62521 1 radeon
drm_kms_helper 27236 1 radeon
drm 202248 3 ttm,drm_kms_helper,radeon
snd_hda_codec_hdmi 31480 1
iTCO_wdt 12832 0
iTCO_vendor_support 12705 1 iTCO_wdt
eeepc_wmi 12601 0
i2c_algo_bit 12842 1 radeon
coretemp 12855 0
i2c_i801 17046 0
kvm_intel 118161 0
mei 31840 0
i2c_core 24042 5 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,radeon
asus_wmi 18804 1 eeepc_wmi
lpc_ich 16758 0
sparse_keymap 12761 1 asus_wmi
rfkill 19167 3 asus_wmi
acpi_cpufreq 13355 1
mperf 12454 1 acpi_cpufreq
mfd_core 12602 1 lpc_ich
snd_hda_codec_realtek 55447 1
snd_hda_intel 30803 5
processor 28456 1 acpi_cpufreq
snd_hda_codec 88216 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep 13190 1 snd_hda_codec
snd_pcm 68524 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 13019 2 snd_pcm,snd_hda_intel
psmouse 69191 0
evdev 17651 6
serio_raw 12941 0
video 17687 1 asus_wmi
kvm 309830 1 kvm_intel
thermal_sys 22342 2 video,processor
wmi 13244 1 asus_wmi
snd_timer 22813 1 snd_pcm
snd 53078 17 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 13027 1 snd
button 12945 0
ext4 371544 1
crc16 12344 1 ext4
jbd2 71913 1 ext4
mbcache 13115 1 ext4
dm_mod 63778 1 dm_crypt
usb_storage 48070 2
sg 26096 0
sd_mod 40550 7
crc_t10dif 12349 1 sd_mod
crc32c_intel 12748 0
ghash_clmulni_intel 13063 0
aesni_intel 50747 0
aes_x86_64 16844 1 aesni_intel
ablk_helper 12573 1 aesni_intel
cryptd 14561 3 ghash_clmulni_intel,aesni_intel,ablk_helper
xts 12723 1 aesni_intel
lrw 12872 1 aesni_intel
gf128mul 13048 2 lrw,xts
microcode 30457 0
xhci_hcd 78154 0
ahci 25061 2
libahci 22919 1 ahci
libata 141636 2 ahci,libahci
ehci_hcd 40532 0
scsi_mod 162399 4 sg,usb_storage,libata,sd_mod
usbcore 134001 5 usb_storage,ehci_hcd,r8712u,usbhid,xhci_hcd
r8169 52700 0
usb_common 12355 1 usbcore
mii 12676 1 r81692u,usbhid,xhci_hcd
r8169 52700 0
usb_common 12355 1 usbcore
mii 12676 1 r8169
Here is an 'iwconfig' output:
eth0 no wireless extensions.
lo no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:"Greenify" Nickname:"rtl_wifi"
Mode:Managed Frequency:2.412 GHz Access Point: 5C:F8:A1:B3:82:5E
Bit Rate:72 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:****-****-****-****-****-****-****-**** Security mode:open
Power Management:off
Link Quality=98/100 Signal level=100/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Here is an lsusb output:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 04e8:61b6 Samsung Electronics Co., Ltd
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter
Bus 004 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 004 Device 005: ID 04d9:a04a Holtek Semiconductor, Inc.
Bus 004 Device 006: ID 0718:053e Imation Corp.
Bus 004 Device 007: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
________________________________________________________________________________________________
I am trying to activate 'monitor mode' on my Wireless USB.
When running 'airmon-ng start wlan0' I get this:
Found 3 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!
-e
PID Name
2508 NetworkManager
2637 wpa_supplicant
2957 dhclient
Process with PID 2635 (wlan0) is running on interface wlan0
Process with PID 2957 (dhclient) is running on interface wlan0
Interface Chipset Driver
wlan0 Unknown r8712u (monitor mode enabled)
Killing those 3 processes with the 'kill <PID>' command does nothing to help.
Also I tried your suggestion of:
# ifconfig wlan0 down
# iw dev wlan0 interface add mon0 type monitor
# ifconfig wlan0 up
And got:
nl80211 not found.
So I tried:
lmsod | grep cfg80211
but instead I got this error:
bash: lmsod: command not found
So I skipped to the next step:
modprobe cfg80211It returned successful by the looks of it.
Then I ran again:
iw dev wlan1 interface add mon0 type monitor
but got the error message:
command failed: Invalid argument (-22)
As you can see from my lsusb and lsmod and iwconfig. I have the USB driver here.
In my /lib/firmware/RTL8192SU I have rtl8192sfw.bin
Not sure if that is the right one seeing as I have the: RTL8191SU
Any ideas guys? This device is so stingy. I can use it to connect to networks without a problem but I cannot start monitor mode on it :(
Also running an 'airmon-ng start wlan0' shows that I seem to be using some sort of 'r8712u' driver or something? Chipset is 'Unknown'
Does anyone have any idea on what is going on?
-
btw, you got a typo in your command when you grep for cfg80211, it's lsmod, not lmsod.
Could you post the dmesg when you plug that adapter? Make sure you boot your computer with the adapter unplugged.
"dmesg -c" then plug the adapter and post the output of dmesg.
-
Yeah the typo was my own typo because I wrote the command out myself in the post here but as you can see I wrote it properly when I ran the command.
Ok here are my dmesg -c outputs. I really want this thing to work if possible. There has to be a workaround of some sort:
Booting without the Wireless adapter connected:
dmesg -chttp://pastebin.com/FxG5QBXv
(Output was too long to post in Forums)
Here is after I connect the Wireless USB adapter:
root@Hidden:~# dmesg -c
[ 210.135701] usb 4-1.1: new high-speed USB device number 6 using ehci_hcd
[ 210.230696] usb 4-1.1: New USB device found, idVendor=0bda, idProduct=8172
[ 210.230701] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 210.230704] usb 4-1.1: Product: RTL8191S WLAN Adapter
[ 210.230707] usb 4-1.1: Manufacturer: Manufacturer Realtek
[ 210.230709] usb 4-1.1: SerialNumber: 00e04c000001
[ 210.279099] r8712u: module is from the staging directory, the quality is unknown, you have been warned.
[ 210.280411] r8712u: Staging version
[ 210.280428] r8712u: register rtl8712_netdev_ops to netdev_ops
[ 210.280431] r8712u: USB_SPEED_HIGH with 4 endpoints
[ 210.280941] r8712u: Boot from EFUSE: Autoload OK
[ 210.777922] r8712u: CustomerID = 0x000a
[ 210.777926] r8712u: MAC Address from efuse = 00:1f:11:10:0a:66
[ 210.777929] r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
[ 210.778021] usbcore: registered new interface driver r8712u
[ 211.543598] r8712u: 1 RCR=0x153f00e
[ 211.544726] r8712u: 2 RCR=0x553f00e
[ 211.651150] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 232.342681] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 232.382872] r8712u: [r8712_got_addbareq_event_callback] mac = 5c:f8:a1:b3:82:5e, seq = 0, tid = 0
Can you see what the problem is?
P.S. I cannot register. The security verifications are really hard.. I've been using backtrack for years now.
But when entering the answers like 'backtrack' (in all lowercase) for what Distro is Kali based off etc. It doesn't work.
-
for one, it looks like you have two drivers loaded for your card, r8169 and r8172u.
also, cfg80211module must be compiled.
you can check by running this command:
$ cat /proc/config.gz | gunzip | grep CFG
-
for one, it looks like you have two drivers loaded for your card, r8169 and r8172u.
r8169 is the Realtek ethernet driver, so nothing wrong there
also, cfg80211module must be compiled.
you can check by running this command:
$ cat /proc/config.gz | gunzip | grep CFG
My output:
CONFIG_CFG80211=m
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
# CONFIG_CFG80211_INTERNAL_REGDB is not set
CONFIG_CFG80211_WEXT=y
and for lsmod | grep cfg80211:
cfg80211 402793 0
rfkill 15698 6 cfg80211,ideapad_laptop,thinkpad_acpi,bluetooth
I have the same "problems" as the others btw. and I fear that this staging driver simply does not support monitor mode, kernel is 3.11.8
A pity there seems no trivial way to check if a driver supports monitoring mode...
-
It's a pity because some cards with this chipset are really good, then can achieve a sensitivity up to -97dBm.
Then, is it confirmed that the chipset doesn't support monitor mode?. Or is just a driver problem?
-
The same problema.Ho decided?