Jump to content

AWUS036NEH working with Kali Rolling


beeps
 Share

Recommended Posts

Hi All,

I know this has probably been mentioned on the internet countless times, but I can't seem to get my AWUS036NEH adapter working with Kali Rolling. I've been at this for days and just can't get my head around it. I'm running Linux kali 4.9.0-kali4-amd64 #1 SMP Debian 4.9.30-1kali1 (2017-06-06) x86_64 GNU/Linux.
I've trawled through forums here and other places and tried various set ups to get this working with no luck, so hopefully someone here can help me out.

Issue: Getting AWUS036NEH adapter to work with Kali Rolling. I can get the device on the system, but I am unable to scan APS (airodump wlan0mon). Although, after trying numerous times to get the adapter working, and keep a log of each step, airodump did work randomly once. (The steps I did will be displayed below)

Setup: Kali is running on Virtualbox VM 5.1.24

Tested the following: Plugged in adapter, selected the USB device to be recognized by Virtual BOX and ran lsusb and can see the device.
Please see below for what I did and got it working, but does not work anymore when I try again. This tells me, that the adapter intermittently works, but am I not understanding or missing something to get it working consistently?
I have each time ran airmon-ng check kill, on each attempt to get it working.

(I've set up the adapter on my MAC OS and it works perfectly fine)


 

Quote

 

root@kali:~# 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

 

ifconfig output
wlan0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 00:c0:ca:95:6f:43  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

 

root@kali:~# airmon-ng start wlan0
PHY    Interface    Driver        Chipset

phy1    wlan0        rt2800usb    Ralink Technology, Corp. RT2870/RT3070

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

 

ifconfig -a
wlan0mon: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        unspec 00-C0-CA-95-6F-43-30-3A-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 132  bytes 32081 (31.3 KiB) <--  RX PACKETS 132 BYTES (prior to this test, it was always zero bytes and now that its not working, its always zero bytes too)
        RX errors 0  dropped 132  overruns 0  frame 0 
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


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

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

 

Ran NetworkManager


root@kali:~# airodump-ng wlan0mon
And now I'm able to see APs!

 

 

But as mentioned, I can't get it to work anymore, can anyone put me in the right direction or help me out?

 

Thanks

 

 

Link to comment
Share on other sites

5 hours ago, Rainman_34 said:

If this is the AC one that is the issue. The AC drivers arent yet comoatable with the linux kernel. They are hoping to have this fixed bu say 6 months from now but the drivers are closed source. 

 I specifically said it's AWUS036NEH......not AC.

 

Link to comment
Share on other sites

Few things, 1, try VMware, not Virtual Box. Virtual Box has issue with wifi dongles, isn't the best for wifi tools, I don't know why, doesn't ever work for me on my system. VMware has great support for USB Wifi dongles, just make sure to pass the USB to the guest system, and you should have a more stable setup. If you get it working in VBox, more power to you, I just don't have the patience for VBox in this respect. Works fine for Kali VM, so long as you don't need wifi capabilities, but that has been my experience. YMMV.

2, what revision of the card do you have? While the card should work out of the box, depending on the chip revision, it won't. I have a TP-Link card, with the same issue, monitor mode doesn't work properly on it, even though its the same TL-WN722N listed to work, only revision V1.0 of my TP link card has drivers, and I have a revision V2.1, so this is something to look into if your card has similar changes to it, it could be the problem with the chipset and no proper driver support and may need to install updated drivers(if available). I had to use some hacked version from github someone wrote, which gave me partial support for AP mode and no proper monitor mode.

3, run airmon-ng check kill. Make sure nothing is causing issues, like dhclient, network manager, wicd, etc. I personally, kill all the network services, samba, etc, and make sure to start the card from airmon like so:

systemctl stop network-manager.service
systemctl stop smbd
killall -9 dhclient
ifconfig wlan0 down
aimon-ng check kill
airmon-ng check
(if nothing listed)
airmon-ng start wlan0
airodump-ng -c # wlan0mon -w dump

In he above airodump-ng command, -c # replace "#" with the channel number you want to capture on. Don't bring it up without selecting a channel, or it hops all 1-14 by default, and doesn't work as well for capturing specific access points and handshakes. You can run it without initially to look for yoru AP, get it's channel #, then stop and restart on that specific channel for best stable results and capturing.

Link to comment
Share on other sites

I downloaded and tried out VMware Fusion and booted the latest Kali 2017.1 light version. I booted into Kali live and still no go with the adapter. It can see the adapter and put it into monitor mode but can not pick up any APs.

What revision card do I have? I'm not sure. There is nothing on the box that indicates a specific version. I know about the TL-WN722N and only version 1 is stable.

I've run airmon-ng check kill and I've run all your commands as well and no luck.

Do you know of any updated (or hacked) drivers for AWUS036NEH ? The current modules that get loaded upon plugging the device in are

rt2800usb
rt2x00usb
rt2800lib
rt2x00lib
mac80211
cfg80211

 

13 hours ago, digip said:

Few things, 1, try VMware, not Virtual Box. Virtual Box has issue with wifi dongles, isn't the best for wifi tools, I don't know why, doesn't ever work for me on my system. VMware has great support for USB Wifi dongles, just make sure to pass the USB to the guest system, and you should have a more stable setup. If you get it working in VBox, more power to you, I just don't have the patience for VBox in this respect. Works fine for Kali VM, so long as you don't need wifi capabilities, but that has been my experience. YMMV.

2, what revision of the card do you have? While the card should work out of the box, depending on the chip revision, it won't. I have a TP-Link card, with the same issue, monitor mode doesn't work properly on it, even though its the same TL-WN722N listed to work, only revision V1.0 of my TP link card has drivers, and I have a revision V2.1, so this is something to look into if your card has similar changes to it, it could be the problem with the chipset and no proper driver support and may need to install updated drivers(if available). I had to use some hacked version from github someone wrote, which gave me partial support for AP mode and no proper monitor mode.

3, run airmon-ng check kill. Make sure nothing is causing issues, like dhclient, network manager, wicd, etc. I personally, kill all the network services, samba, etc, and make sure to start the card from airmon like so:


systemctl stop network-manager.service
systemctl stop smbd
killall -9 dhclient
ifconfig wlan0 down
aimon-ng check kill
airmon-ng check
(if nothing listed)
airmon-ng start wlan0
airodump-ng -c # wlan0mon -w dump

In he above airodump-ng command, -c # replace "#" with the channel number you want to capture on. Don't bring it up without selecting a channel, or it hops all 1-14 by default, and doesn't work as well for capturing specific access points and handshakes. You can run it without initially to look for yoru AP, get it's channel #, then stop and restart on that specific channel for best stable results and capturing.

 

Link to comment
Share on other sites

I know that with my TP-Link card, it is on the back of the card itself, shows the revision # as V2.1. On the Alpha cards, mine doesn't show anything like that, but I have an AR9271 based AWUS036NHA that works fine for me.

 

One thing I want you to try. Boot a real machine with a live disc of Kali and try it while in live mode. Not from a VM, but form real hardware, either with your desktop or if you have a laptop. Plug the card in, do a dmesg, make sure it was seen, then try the above I posted before, kill network service, run airmon-ng check, kill any thing it lists, then start the card in monitor mode, and when running airodump-ng, be sure to set the channel your AP is on with  -c # where # is the channel number. 

I know that sounds weird, but I want to rule something out. Also what version of USB is the machine(real hardware, not VM). Make sure USB 2.0 is enabled in the bios if you can. If 3.0, try a 2.0 slot if you have each. If it's a 1.0 or 1.1, not sure it will work 100%. Same goes for the VM, you might have to actually tell it to use 1.0 and not 2.0 on the VM itself, but using native hardware in a Live disc boot, should give us a better idea what happens. If it doesn't work there, then it's not the VM, it may be the actual machine itself, or the card version you have, is just a flake and not going to work without proper firmware and drivers for whatever is required for the chipset. You can see people with the same card, having issues, and others not, so it's definitely hit or miss with the NEH models of the card, just not sure all the factors involved that cause the flaky issues.

Edited by digip
Link to comment
Share on other sites

Hi everyone, first post, so: Hello :)

got exactly the same issue here with a AWUS036NEH on Kali, newest release, VMWARE Fusion on MacOS. Stick is recognized, but can’t see any networks nor works in monitor mode. On MacOS the stick works fine but can’t monitor either as for the limitations of the airport utilitiy only for internal wifi cards. Any advice would be great

Link to comment
Share on other sites

Tried around a bit today and found out, that this seems to be a issue with switching from AP mode to Monitor mode and vice versa:

root@kali:~# uname -a
Linux kali 4.9.0-kali4-amd64 #1 SMP Debian 4.9.30-2kali1 (2017-06-22) x86_64 GNU/Linux

root@kali:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0mon  IEEE 802.11  Mode:Monitor  Frequency:2.457 GHz  Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          

root@kali:~# iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
eth0      no wireless extensions.

root@kali:~# iwlist scan
lo        Interface doesn't support scanning.

wlan0     No scan results

eth0      Interface doesn't support scanning.

root@kali:~# airmon-ng start wlan0

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
   495 NetworkManager
   598 dhclient
   839 wpa_supplicant

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@kali:~# airodump-ng -c 6 wlan0mon

 CH  6 ][ Elapsed: 6 s ][ 2017-08-06 13:01                                         
                                                                                                                                                
 BSSID              PWR RXQ  Beacons    #Data, #/s  CH  MB   ENC  CIPHER AUTH ESSID
                                                                                                                                                
                                                                                                                                                
 BSSID              STATION            PWR   Rate    Lost    Frames  Probe                                                                      
                                                                                                       

root@kali:~# ifconfig 
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.178.50  netmask 255.255.255.0  broadcast 192.168.178.255
        inet6 fe80::20c:29ff:fe59:1a61  prefixlen 64  scopeid 0x20<link>
        inet6 2a02:810d:2a40:520:d153:c5db:b464:ab6c  prefixlen 64  scopeid 0x0<global>
        inet6 2a02:810d:2a40:520:20c:29ff:fe59:1a61  prefixlen 64  scopeid 0x0<global>
        ether 00:0c:29:59:1a:61  txqueuelen 1000  (Ethernet)
        RX packets 2776  bytes 1777366 (1.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1403  bytes 335622 (327.7 KiB)
        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  (Lokale Schleife)
        RX packets 129  bytes 15201 (14.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 129  bytes 15201 (14.8 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-C0-CA-95-6C-EF-30-3A-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        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


Then, unplug the USB Stick and Plug in again:
root@kali:~# iwlist scan
lo        Interface doesn't support scanning.

wlan0     Failed to read scan data : Network is down

eth0      Interface doesn't support scanning.

root@kali:~# iwlist scan
lo        Interface doesn't support scanning.

wlan0     Interface doesn't support scanning : Device or resource busy

eth0      Interface doesn't support scanning.

root@kali:~# iwlist scan
lo        Interface doesn't support scanning.

wlan0     Interface doesn't support scanning : Device or resource busy

eth0      Interface doesn't support scanning.


root@kali:~# iwlist scan
lo        Interface doesn't support scanning.

wlan0     Scan completed :
          Cell 01 - Address: E4:18:6B:8B:F5:DE
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=33/70  Signal level=-77 dBm  
                    Encryption key:on
                    ESSID:"intern34"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=000001541d04c151
                    Extra: Last beacon: 13720ms ago
                    IE: Unknown: 0008696E7465726E3334
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 030101
                    IE: Unknown: 32040C183060
                    IE: Unknown: 0706444520010D14
                    IE: Unknown: 33082001020304050607
                    IE: Unknown: 33082105060708090A0B
                    IE: Unknown: 050400010000
                    IE: Unknown: DD310050F204104A0001101044000102104700102880288028801880A880E4186B8BF5DE103C0001011049000600372A000120
                    IE: Unknown: 2A0104
                    IE: Unknown: 2D1A6E1017FFFF0000010000000000000000000000000C0000000000
                    IE: Unknown: 3D1601000600000000000000000000000000000000000000
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: 7F0101
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: 0B05010003127A
                    IE: Unknown: DD07000C4304000000

<snip>

          Cell 02 - Address: 5C:49:79:70:7A:74
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=41/70  Signal level=-69 dBm  
                    Encryption key:on
                    ESSID:"Kalb1920"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000000001bdff83
                    Extra: Last beacon: 7484ms ago
                    IE: Unknown: 00084B616C6231393230
                    IE: Unknown: 010882848B968C129824
                    IE: Unknown: 030101
                    IE: Unknown: 0706444520010D14
                    IE: Unknown: 2A0100
                    IE: Unknown: 3204B048606C
                    IE: Unknown: 2D1AAD011BFFFFFF00000000000000000001000000000406E6470D00
                    IE: Unknown: 3D1601000100000000000000000000000000000000000000
                    IE: Unknown: 7F080000000000000040
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: DD0900037F01010000FF7F
                    IE: Unknown: DD0C00040E010102010000000000
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 


And: Voila, i can see other networks. Then, i switch to monitor mode, just to see nothing again:

root@kali:~# airmon-ng start wlan0

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
   495 NetworkManager
   598 dhclient
   839 wpa_supplicant

PHY    Interface    Driver        Chipset

phy1    wlan0        rt2800usb    Ralink Technology, Corp. RT2870/RT3070

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

root@kali:~# airodump-ng -c 6 wlan0mon

 CH  6 ][ Elapsed: 18 s ][ 2017-08-06 13:10                                         
                                                                                                                                                
 BSSID              PWR RXQ  Beacons    #Data, #/s  CH  MB   ENC  CIPHER AUTH ESSID
                                                                                                                                                
                                                                                                                                                
 BSSID              STATION            PWR   Rate    Lost    Frames  Probe                                                                      
                                                                                                                                                

root@kali:~# airmon-ng stop wlan0

PHY    Interface    Driver        Chipset

phy1    wlan0mon    rt2800usb    Ralink Technology, Corp. RT2870/RT3070


root@kali:~# airmon-ng stop wlan0mon

PHY    Interface    Driver        Chipset

phy1    wlan0mon    rt2800usb    Ralink Technology, Corp. RT2870/RT3070

        (mac80211 station mode vif enabled on [phy1]wlan0)

        (mac80211 monitor mode vif disabled for [phy1]wlan0mon)

root@kali:~# ifconfig 
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.178.50  netmask 255.255.255.0  broadcast 192.168.178.255
        inet6 fe80::20c:29ff:fe59:1a61  prefixlen 64  scopeid 0x20<link>
        inet6 2a02:810d:2a40:520:d153:c5db:b464:ab6c  prefixlen 64  scopeid 0x0<global>
        inet6 2a02:810d:2a40:520:20c:29ff:fe59:1a61  prefixlen 64  scopeid 0x0<global>
        ether 00:0c:29:59:1a:61  txqueuelen 1000  (Ethernet)
        RX packets 3884  bytes 1864850 (1.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2208  bytes 849044 (829.1 KiB)
        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  (Lokale Schleife)
        RX packets 129  bytes 15201 (14.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 129  bytes 15201 (14.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 96:3d:9b:82:b2:92  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

root@kali:~# iwlist scan
lo        Interface doesn't support scanning.

wlan0     Interface doesn't support scanning : Device or resource busy

eth0      Interface doesn't support scanning.

root@kali:~# iwlist scan
lo        Interface doesn't support scanning.

wlan0     No scan results

eth0      Interface doesn't support scanning.


 

Link to comment
Share on other sites

8 hours ago, digip said:

 

I know that with my TP-Link card, it is on the back of the card itself, shows the revision # as V2.1. On the Alpha cards, mine doesn't show anything like that, but I have an AR9271 based AWUS036NHA that works fine for me.

 

One thing I want you to try. Boot a real machine with a live disc of Kali and try it while in live mode. Not from a VM, but form real hardware, either with your desktop or if you have a laptop. Plug the card in, do a dmesg, make sure it was seen, then try the above I posted before, kill network service, run airmon-ng check, kill any thing it lists, then start the card in monitor mode, and when running airodump-ng, be sure to set the channel your AP is on with  -c # where # is the channel number. 

I know that sounds weird, but I want to rule something out. Also what version of USB is the machine(real hardware, not VM). Make sure USB 2.0 is enabled in the bios if you can. If 3.0, try a 2.0 slot if you have each. If it's a 1.0 or 1.1, not sure it will work 100%. Same goes for the VM, you might have to actually tell it to use 1.0 and not 2.0 on the VM itself, but using native hardware in a Live disc boot, should give us a better idea what happens. If it doesn't work there, then it's not the VM, it may be the actual machine itself, or the card version you have, is just a flake and not going to work without proper firmware and drivers for whatever is required for the chipset. You can see people with the same card, having issues, and others not, so it's definitely hit or miss with the NEH models of the card, just not sure all the factors involved that cause the flaky issues.

 

Ok, I got some good news,

Booted up Kali 2017.1 light on a bootable usb on my other laptop.
Put in the wireless card, and dmesg and lsusb shows card is detected.
airmon-ng start wlanX (X being your numbered device )
airodump-ng wlanX and APs show up!
I stopped everything and tried it again and it works perfectly.


This suggests to me now that this has something to do with the VMWare and VirtualBox running Kali inside a VM. Probably a setting, or doesn't read the hardware or drivers correctly ? What's your thoughts on this digip? Surely other people are experiencing this issue with the VM applications. Maybe, they are using other wifi compatible devices that work well the VM applications beside the AWUS036NEH device.

 

 

Link to comment
Share on other sites

2 minutes ago, beeps said:

 

Ok, I got some good news,

Booted up Kali 2017.1 light on a bootable usb on my other laptop.
Put in the wireless card, and dmesg and lsusb shows card is detected.
airmon-ng start wlanX (X being your numbered device )
airodump-ng wlanX and APs show up!
I stopped everything and tried it again and it works perfectly.


This suggests to me now that this has something to do with the VMWare and VirtualBox running Kali inside a VM. Probably a setting, or doesn't read the hardware or drivers correctly ? What's your thoughts on this digip? Surely other people are experiencing this issue with the VM applications. Maybe, they are using other wifi compatible devices that work well the VM applications beside the AWUS036NEH device.

 

 

Which Version of VMWare Fusion / MacOS you´re running? 

 

Link to comment
Share on other sites

Solved it (for now): a simple airmon-ng check kill did the trick. Now i can see networks in airodump. 

Running VMWare Fusion 8.1.0, MacOS 10.12.6

Sorry for thread-hijacking beeps and thanks for the conclusion with Live Kali 2017.1 from stick, will try this in addition 

Link to comment
Share on other sites

28 minutes ago, JohnDoeY said:

Solved it (for now): a simple airmon-ng check kill did the trick. Now i can see networks in airodump. 

Running VMWare Fusion 8.1.0, MacOS 10.12.6

Sorry for thread-hijacking beeps and thanks for the conclusion with Live Kali 2017.1 from stick, will try this in addition 

I too ran airmon-ng check kill but didn't do much for me.
Is airodump-ng consistent after running the airmon-ng check kill command?

 

Link to comment
Share on other sites

Just now, beeps said:

I too ran airmon-ng check kill but didn't do much for me.
Is airodump-ng consistent after running the airmon-ng check kill command?

 

yes, runs fine. I run check kill now before doing anything else, hit the same problem with fluxion, check kill solves it

Link to comment
Share on other sites

3 minutes ago, JohnDoeY said:

yes, runs fine. I run check kill now before doing anything else, hit the same problem with fluxion, check kill solves it

hmm, perhaps I should downgrade VMWare Fusion and upgrade macosx

Link to comment
Share on other sites

Also, check what USB settings are enabled for the VM. if your box only has USB 3.0, this might be an issue(from some googling at others with issues). Try setting the VM to use USB v1.1, or 2.0, and make sure in the bios it's capable. USB 3.0 only might not have great support in the VM's, so making sure to set one or the other and try again, see what happens.

Link to comment
Share on other sites

7 hours ago, digip said:

Also, check what USB settings are enabled for the VM. if your box only has USB 3.0, this might be an issue(from some googling at others with issues). Try setting the VM to use USB v1.1, or 2.0, and make sure in the bios it's capable. USB 3.0 only might not have great support in the VM's, so making sure to set one or the other and try again, see what happens.

I've tested each USB settings in VirtualBox. 1.1 / 2.0 / 3.0 with the wifi adapter and doesn't work for airodump-ng.

At least this points me in the right direction....It has to do something with the VM compatibility with the hardware. It seems JohnDoey got it working fine with a lower version VMWare Fusion and upgraded mac os x.

Link to comment
Share on other sites

Being that it works with the native hardware outside the VM, I'm going to chalk this one up to the MAC OS compatibility with timing on the USB devices. Not necessarily so much a Kali thing, but more between the host and guest side of the virtualization software causing your pain. I have a windows box, so not sure how a MAC handles the VM's, but if you don't have the machine full screened and instead is windowed, I wonder if when the mouse cursor leaves and enters the VM, if it loses focus and the USB is switching back and forth between the HOST and GUEST machine. Make sure the VM is set to automatically send the USB to the guest upon plugging in, and never plug in the USB until the VM has full screen focus. If connected to the host first and then passed to the VM, this might make things a bit hardware to figure out where the problem is.

All else fails, use the laptop as the main attack machine on native hardware, and use the other box to run your VM's of vulnerable test machines so you can attack from the Live booted kali to have full use of the hardware as expected. 

Link to comment
Share on other sites

On 07/08/2017 at 11:26 AM, digip said:

Being that it works with the native hardware outside the VM, I'm going to chalk this one up to the MAC OS compatibility with timing on the USB devices. Not necessarily so much a Kali thing, but more between the host and guest side of the virtualization software causing your pain. I have a windows box, so not sure how a MAC handles the VM's, but if you don't have the machine full screened and instead is windowed, I wonder if when the mouse cursor leaves and enters the VM, if it loses focus and the USB is switching back and forth between the HOST and GUEST machine. Make sure the VM is set to automatically send the USB to the guest upon plugging in, and never plug in the USB until the VM has full screen focus. If connected to the host first and then passed to the VM, this might make things a bit hardware to figure out where the problem is.

All else fails, use the laptop as the main attack machine on native hardware, and use the other box to run your VM's of vulnerable test machines so you can attack from the Live booted kali to have full use of the hardware as expected. 

I tend to agree. It seems though even though VB or VmwareFusion have mac compatibility, the host to guest shouldn't be an issue. Who knows. I think the best outcome would be to just use a dedicated laptop and hardware and VMs for testing. Thanks for help and appreciate the feedback.

Link to comment
Share on other sites

I tested the latest VMWare Fusion AND MacOS Version together today on my wifes MacBook, again: no issues. Works like it should. So its: three devices with different patch levels and all the same Kali and the same antenna. Maybe your USB Port, the USB Cable or the MacBook himself got issues? The tree devices i tested on are:

MacBook Pro, 15", Late 2009
MacBook Pro, 15", Mid 2010
MacBook Pro, 15", Mid 2014

 

Link to comment
Share on other sites

  • 3 years later...

2020-Oct UPDATE: ALFA AWUS036NEH WiFi Running under VMWare Kali Linux 2020.1 SOLUTION with inconsistency: change options simply from USB 2.0  => USB 3.1

Had the same issue and even was looking to update the drivers, although it would probably not help as these are the latest drivers anyhow.

Setup: Host Windows 8.1 ver 6.3.9600 running VMWare Player 16 Kali Linux 2020.1 with Alfa AWUS036NEH USB, i7 CPU

Problem (very similar to topic):

At start the dingle works fine. First monitor mode also works. First airodump-ng shows all networks.  After that the issues start.

No more airodump-ng possible, no successive scans possible etc. The inconsistency leads someone to believe it is a Kali problem of not recognizing or installing the card properly. It does not seem to be the case.

Solution:

Thanks for the tip on looking in the USB Virtual machine setting. As it is clearly recommended in many places & tutprials to "match" the WiFi dongle to it's native USB2.0 state this seems exactly to not run consistently. Switching to USB3.1 in the VMWare setting fixes everything and all scans work continuously and consistently multiple times. It is not the drivers, nor Kali, nor the VM software itself.

Let me know if questions. glasfactor@gmail.com

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...