I have had mixed results as well, bad .cap file or what seems to look like good signal is not good enough to capture a handshake properly. Works great in windows environment lol. Works in kali as well, just a pita.
Printable View
Well I finally have my 036ACH working now. Packet injection is good, airmon-ng works! Finally time to have some fun. Big thanks to everyone who contributed.
Soo what was the final setup that was agreed upon to get this working? (as best as possible I mean) ? a summary would be greatly appreciated
2018.3 is what seemed to be working for me. If you look at the bug fixes the drivers install was fixed. After installing a fresh Kali 2018.3 I just did everything listed.
- apt-get update && upgrade commands
- After update was completed I went ahead and installed the dkms files
- Quick Reboot
- Then I installed the github files.
- Uninstalled the dkms files and reinstalled.
- Cards blue light finally kicked on and I could see wifi. Packet injection and monitor mode worked great.
After your reboot did you try and do a second upgrade, just to make sure everything was installed? Also are you running on a live usb?
I realised my error after posting but wasn't able to edit it as it hadn't been approved yet - I had the USB controller in VMWare set to 'USB 2.0' so of course it didn't work correctly.
However, I cannot get airmon-ng to work on the card; I get the following output:
Same thing happens if I run 'airmon-ng check kill' first...Code:root@kali:~# airmon-ng start wlan0
PHY Interface Driver Chipset
phy0 wlan0 8812au Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter
cat: /sys/class/ieee80211/phy0/device/net/wlan0mon/type: No such file or directory
Newly created monitor mode interface wlan0mon is *NOT* in monitor mode.
Removing non-monitor wlan0mon interface...
WARNING: unable to start monitor mode, please run "airmon-ng check kill"
Does it work for you?
Sorry I am not the biggest help with Kali. Just now getting back into it. It is currently working for me. However, went ahead and did a full GUI install on a spare HDD I had in my computer. Have you tried this?
ip link set wlan1 down
iwconfig wlan1 mode monitor
ip link set wlan1 up
iwconfig wlan1 txpower 30
iwconfig | grep wlan1
. Using Kali linux 64bit vmware
. Updated to latest version with
Apt update
apt dist-upgrade
reboot
Airmon-ng not working returns with msg /sys/.... file not found , permission denied
Airdump-ng also not working gets stuck when i run command then i have to reboot.
If enable monitoring mode on wlan0 , throught iwconfig , then i tried airdump-ng thats when it get stuck. Other then that i can see my wlan in iconfig and iwconfig and through GUI i can see networks as well
Any fix out there?
If there is a kind soul who would post step-by-step instructions on how to get these drivers up on a clean 2018.3 Kali install, I would be very very grateful. And I am certain there are many others for whom such a guide would be helpful. I have been trying to get this adapter up for 3 weeks now. Call me a dumb noob, but statements like ""Installed the dkms files / installed the github files / Uninstalled the dkms files and reinstalled" are not helpful to me.
Thank you very much
RadioGirl
Here's what I did to finally get it working:
• Clean install Kali 2018.3 - If not clean, run: apt remove realtek-rtl88xxau-dkms && apt purge realtek-rtl88xxau-dkms
• apt update && apt upgrade
• apt autoremove && apt autoclean
• reboot
• apt-get dist-upgrade
• reboot
• git clone https://github.com/kimocoder/rtl8812au
• cd rtl8812au
• make && make install
• poweroff
• Plug in AWUS036ACH into a USB2 port - Ensure that USB 2.0(EHCI) Controller is used in machine settings.
• Power up, after logging in confirm with iwconfig - If still not working, reset the machine via VBox.
For some reason USB3 wouldn't work for me, VBox wouldn't connect the NIC at all, or I was getting descriptor errors in dmesg. USB2 is working perfectly fine. Packet injection working. 5ghz deauth and handshake captured.
Hello!
Still cannot get past this error after make with kimocoder's driver:
/bin/sh: 1: bc: not found
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.18.0-kali2-amd64/build M=/root/rtl8812au modules
make[1]: *** /lib/modules/4.18.0-kali2-amd64/build: No such file or directory. Stop.
make: *** [Makefile:1918: modules] Error 2
apt install bc linux-headers-$(uname -r) gives this result:
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package bc
E: Unable to locate package linux-headers-4.18.0-kali2-amd64
E: Couldn't find any package by glob 'linux-headers-4.18.0-kali2-amd64'
E: Couldn't find any package by regex 'linux-headers-4.18.0-kali2-amd64'
Can anyone please help me out?
apt update && apt dist-upgrade then reboot and try again installing the drivers.
Well well, I'm not good at forums at all, this thread ran straight over my head.
Anyways, got some interesting updates to the drivers ready soon. Saving them into one PR and shove them in after some testing.
The TODO list is available to see at
https://github.com/aircrack-ng/rtl8812au/pull/246
with a possible increase of range could be in sight, duo to a antenna (diversity) bug. we'll see in a few days, I'm get back to my desk again.
Cheers
Another little note, my repo at https://github.com/kimocoder/rtl8812au is experimental, a playground from where I push the finished/working PR to aircrack-ng repo.
So avoid using my private, it would only result in issues
The aircrack-ng repo should be used ☺️
The problem also exists in my setup. I have tried everything this forum and nothing. 2 weeks have passed and I've tried in VMware, Virtual Box with so many different installs and configurations and no luck at all. By the way, I have a Windows 10 laptop.
Thanks! This worked for me! I found after reading a number of posts I had a similar problem to someone else here (I can't find that post now) where I had 2 version of the realtek driver installed.
"dmesg | grep 8812au" showed 2 version of the driver.
Following Hercule's advice fixed it for me.