AIrodump-ng capture problems in kali 2.0 and VirtualBox

[Fushikkles]

I have checked other forums and i have a situation which is not consistent in its solution methods. It seems that most of the time i am able to run airmon-ng, airmon-ng check, airmon-ng check kill and then start wlan0mon. I have no issues there. It's when i get running airodump-ng wlan0mon to test that i get persistent issues. The warnings that get thrown up are ‘ioctl(SIOCSIWMODE)' and on some occassions 'Failed to set wlan0mon up using ip', and failed: Device or resource busy ‘.

What is frustrating is even after trying solutions like this: (in my case wlan0); sudo ifconfig wlan2 down, sudo iwconfig wlan2 mode monitor, sudo ifconfig wlan2 up, sudo iwconfig wlan2; nothing happens. See; https://uwnthesis.wordpress.com/2013...-busy-problem/; https://taufanlubis.wordpress.com/20...-busy-problem/; http://stackoverflow.com/questions/3...on-doesnt-work; http://null-byte.wonderhowto.com/for...-work-0165278/; howver, i havent tried this yet, https://forums.kali.org/showthread.p...rkManager-conf.

It's more than a little annoying because i'm writing this it's working fine. I started up airmon-ng this morning and airodump is working fine... but i suspect some process is interfering: E.g.,

[QUOTE]root@kali2:~# airmon-ng

PHY Interface Driver Chipset

phy0 wlan0 rt2800usb Ralink Technology, Corp. RT2870/RT3070

root@kali2:~# airmon-ng check

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 run 'airmon-ng check kill'

PID Name
554 NetworkManager
709 wpa_supplicant
715 dhclient

root@kali2:~# airmon-ng check kill

Killing these processes:

PID Name
709 wpa_supplicant
715 dhclient

root@kali2:~# airmon-ng start wlan0


PHY Interface Driver Chipset

phy0 wlan0 rt2800usb Ralink Technology, Corp. RT2870/RT3070

(mac80211 monitor mode vif enabled for [phy0]wlan0 on [phy0]wlan0mon)
(mac80211 station mode vif disabled for [phy0]wlan0)

root@kali2:~# airodump-ng -c wlan0mon

My system details are as follows:

root@kali2:~# lsb_release -a
No LSB modules are available.
Distributor ID:	Kali
Description:	Kali GNU/Linux Rolling
Release:	kali-rolling
Codename:	kali-rolling
root@kali2:~# ls -d /etc/* | grep release
/etc/lsb-release
/etc/os-release
root@kali2:~#  cat /etc/*{release,version}
DISTRIB_ID=Kali
DISTRIB_RELEASE=kali-rolling
DISTRIB_CODENAME=kali-rolling
DISTRIB_DESCRIPTION="Kali GNU/Linux Rolling"
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
ID=kali
VERSION="2016.1"
VERSION_ID="2016.1"
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.kali.org/"
SUPPORT_URL="http://forums.kali.org/"
BUG_REPORT_URL="http://bugs.kali.org/"
Kali Linux Rolling
cat: /etc/subversion: Is a directory
root@kali2:~# /etc/<distro>-release
bash: distro: No such file or directory
root@kali2:~#  ls -d /etc/* | grep version
/etc/debian_version
/etc/subversion
root@kali2:~# lsb_release -a
No LSB modules are available.
Distributor ID:	Kali
Description:	Kali GNU/Linux Rolling
Release:	kali-rolling
Codename:	kali-rolling
root@kali2:~# cat /etc/issue
Kali GNU/Linux Rolling \n \l
root@kali2:~# 

Iwconfig:

root@kali2:~# iwconfig
eth0      no wireless extensions.

eth1      no wireless extensions.

wlan0mon  IEEE 802.11bgn  Mode:Monitor  Frequency:2.412 GHz  Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          
lo        no wireless extensions.

Ifconfig:

root@kali2:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.7  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::a00:27ff:fe30:92af  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:30:92:af  txqueuelen 1000  (Ethernet)
        RX packets 34045  bytes 21608912 (20.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 26349  bytes 5310582 (5.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 08:00:27:8f:f9:3a  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 20  bytes 1200 (1.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 20  bytes 1200 (1.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0mon: flags=867<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,ALLMULTI>  mtu 1500
        unspec 00-25-22-4E-CE-58-3A-30-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 141153  bytes 14843869 (14.1 MiB)
        RX errors 0  dropped 8044  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lspci

root@kali2:~# lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter
00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service
00:05.0 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio Controller (rev 01)
00:06.0 USB controller: Apple Inc. KeyLargo/Intrepid USB
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
00:08.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
00:0b.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller
00:0d.0 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 02)

[Fushikkles]

lsusb:

root@kali2:~# lsusb
Bus 001 Device 002: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

dmesg:

root@kali2:~# dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.0-kali1-amd64 ([email protected]) (gcc version 5.3.1 20160307 (Debian 5.3.1-11) ) #1 SMP Debian 4.4.6-1kali1 (2016-03-18)
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-kali1-amd64 root=UUID=2f18133f-71a8-4c9a-9996-e6302399f54d ro initrd=/install/initrd.gz quiet

[   35.016031] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 detected
[   35.666575] cfg80211: World regulatory domain updated:
[   35.666588] cfg80211:  DFS Master region: unset
[   35.666593] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   35.666601] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   35.666608] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   35.666614] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   35.666621] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   35.666628] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   35.666634] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[   35.666640] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   35.666646] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[   35.869703] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
[   35.953411] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   35.954502] usbcore: registered new interface driver rt2800usb
[   43.439187] Bluetooth: Core ver 2.21
[   43.439218] NET: Registered protocol family 31
[   43.439220] Bluetooth: HCI device and connection manager initialized
[   43.439225] Bluetooth: HCI socket layer initialized
[   43.439228] Bluetooth: L2CAP socket layer initialized
[   43.439235] Bluetooth: SCO socket layer initialized
[   43.462877] Netfilter messages via NETLINK v0.30.
[   45.522965] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   45.523231] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[   45.886333] rt2800usb 1-1:1.0: firmware: direct-loading firmware rt2870.bin
[   45.886360] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29
[   51.185609] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   51.190942] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   51.193854] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   51.198868] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   51.281448] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[   51.282464] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   51.282498] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   56.170118] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  101.570933] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  101.570944] Bluetooth: BNEP filters: protocol multicast
[  101.570958] Bluetooth: BNEP socket layer initialized
[  153.277201] fuse init (API version 7.23)
[  496.054414] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[  605.411811] device wlan0mon entered promiscuous mode

VIrtualBox version: 5.0.16 r 105871

[viv24]

I encountered the same problem as you and also have the same configuration. Did you resolve the problem.If so, can you please help me out

[_defalt]

I encountered the same problem as you and also have the same configuration. Did you resolve the problem.If so, can you please help me out

What commands did you enter?