beeps
-
Posts
9 -
Joined
-
Last visited
Posts posted by beeps
-
-
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.
-
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
-
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? -
7 minutes ago, JohnDoeY said:
Which Version of VMWare Fusion / MacOS you´re running?
vmware fusion - 8.5.8
mac osx 10.11.5 -
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. -
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
cfg8021113 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.
-
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.
-
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)
Quoteroot@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 hubifconfig 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 0root@kali:~# airmon-ng start wlan0
PHY Interface Driver Chipsetphy1 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
AWUS036NEH working with Kali Rolling
in Questions
Posted
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.