How to install AWUS036ACH Drivers and getting it running?

[d8932]

Hi everyone,

I have the ALFA AWUS036ACH wireless USB adapter and the latest version of Kali (2017.1 + updates), I did "apt install realtek-rtl88xxau-dkms" as pointed here but the system still doesn't seem to be able to detect the device at all.

I've tried on Windows and it's detected just fine, but when I try on a Linux system Kali or otherwise I'm unable to get it running.

any advice from someone who has the same device?


Thank you so much

[lostincynicism]

Yeah, I just installed the kernel drivers (kali is completely updated) and I am having the same issue. Dmesg sees it, but I can't modify it with ifconfig, nor does the wireless menu list any other devices to use.

usb 1-2: new high-speed USB device number 5 using xhci_hcd
usb 1-2: New USB device found, idVendor=0bda, idProduct=8812
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2: Product: 802.11n NIC
usb 1-2: Manufacturer: Realtek
usb 1-2: SerialNumber: 123456
usb 1-2: USB disconnect, device number 5

[kcdtv]

If the drivers isn't launched automatically do

(sudo) modprobe 8812au

if network-manager does not see it afterward do

(sudo) systemctl restart network-manager

[user55661]

If the drivers isn't launched automatically do

(sudo) modprobe 8812au

if network-manager does not see it afterward do

(sudo) systemctl restart network-manager

mine is also doing the same thing as everyone else's here (ie shows up in dmesg but not iwconfig). This didn't fix it :/

I got a

modprobe: ERROR: could not insert '8812au': Exec format error
root@kali:~# sudo modprobe 8812au


I tried --force but that still didn't work. Oh well that's why I'm using a VM.

[kcdtv]

I don't understand what you mean by " Oh well that's why I'm using a VM. ". If you use a VM you need to enable USB 3.0 support otherwise the device won't work.
Install the source code from the drivers instead of the dkms package if that doesn't work for you: astsam/rtl8812au
Don't forget to remove the dkms package first (with apttitude itself) to avoid conflicts

[user55661]

It also does the exact same thing on a regular Kali system

[5M7X]

I also followed the hint in the blogpost on kali.org https://www.kali.org/news/kali-linux-20171-release/

For me it also fails unfortunately:

root@kali:~# apt-get update
Hit:1 http://archive-3.kali.org/kali kali-rolling InRelease
Reading package lists... Done
root@kali:~# apt install realtek-rtl88xxau-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
gdebi-core gnome-mime-data gnome-shell-extension-refreshwifi iproute libbonobo2-0 libbonobo2-common libcrypto++6 libgles1-mesa libgnome-2-0 libgnome2-common libgnomevfs2-0 libgnomevfs2-common
libgnomevfs2-extra libjavascriptcoregtk-1.0-0 libladr4 liblircclient0 libminizip1 libnm-gtk-common liborbit-2-0 libqt4-opengl libqtwebkit4 libre2-3 libvpx3 libwebkitgtk-1.0-0 prover9 python-clamd
python-cluster python-d2to1 python-darts-lib-utils-lru python-defusedxml python-esmre python-git python-gitdb python-guess-language python-halberd python-ipaddr python-ndg-httpsclient python-nltk
python-pdfminer python-phply python-ply python-psutil python-pybloomfiltermmap python-pycryptopp python-pygithub python-pypdf python-ruamel.ordereddict python-smmap python-soappy python-stopit python-svn
python-tblib python-vulndb python-webkit python-wstools python-xdot rsync w3af w3af-console
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
realtek-rtl88xxau-dkms
0 upgraded, 1 newly installed, 0 to remove and 375 not upgraded.
Need to get 1,522 kB of archives.
After this operation, 14.8 MB of additional disk space will be used.
Get:1 http://archive-3.kali.org/kali kali-rolling/contrib amd64 realtek-rtl88xxau-dkms all 4.3.21~20170330-0kali1 [1,522 kB]
Fetched 1,522 kB in 4s (341 kB/s)
Selecting previously unselected package realtek-rtl88xxau-dkms.
(Reading database ... 342049 files and directories currently installed.)
Preparing to unpack .../realtek-rtl88xxau-dkms_4.3.21~20170330-0kali1_all.deb ...
Unpacking realtek-rtl88xxau-dkms (4.3.21~20170330-0kali1) ...
Setting up realtek-rtl88xxau-dkms (4.3.21~20170330-0kali1) ...
Loading new realtek-rtl88xxau-4.3.21~20170330 DKMS files...
Building for 4.6.0-kali1-amd64
Module build for kernel 4.6.0-kali1-amd64 was skipped since the
kernel headers for this kernel does not seem to be installed.
root@kali:~# uname -a
Linux kali 4.6.0-kali1-amd64 #1 SMP Debian 4.6.4-1kali1 (2016-07-21) x86_64 GNU/Linux
root@kali:~# cat /etc/issue
Kali GNU/Linux Rolling \n \l
root@kali:~# lsusb
Bus 001 Device 004: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor
Bus 001 Device 003: ID 8087:07dc Intel Corp.
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 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 002 Device 005: ID 413c:81a3 Dell Computer Corp.
Bus 002 Device 004: ID 0c45:64d2 Microdia
Bus 002 Device 003: ID 1532:0001 Razer USA, Ltd RZ01-020300 Optical Mouse [Diamondback]
Bus 002 Device 006: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I tried to manualla load the driver as well.

root@kali:~# modprobe 8812au
modprobe: FATAL: Module 8812au not found in directory /lib/modules/4.6.0-kali1-amd64

But it is not there since it failed to built as you can see in the install-log.
So I am confused do I have to built the drivers myself despite the blogpost states it should work out of the box?

[kcdtv]

Module build for kernel 4.6.0-kali1-amd64 was skipped since the
kernel headers for this kernel does not seem to be installed.

Install the headers

sudo apt install linux-headers-amd64

[d8932]

If the drivers isn't launched automatically do

(sudo) modprobe 8812au

if network-manager does not see it afterward do

(sudo) systemctl restart network-manager

Thank you so much! modprobe worked!
device now working as it should.

mine is also doing the same thing as everyone else's here (ie shows up in dmesg but not iwconfig). This didn't fix it :/

I got a

modprobe: ERROR: could not insert '8812au': Exec format error
root@kali:~# sudo modprobe 8812au


I tried --force but that still didn't work. Oh well that's why I'm using a VM.

As for this issue, I've had the same thing happen to me on another VM, what I did to fix it was uninstall the drivers then reinstall them, don't know why but it worked.

apt-get remove realtek-rtl88xxau-dkms
apt-get purge realtek-rtl88xxau-dkms

then reinstall

apt-get install realtek-rtl88xxau-dkms

[dmatrix]

I'm using the version here 5.1.5:
root@kali:~# uname -r
4.9.0-kali4-amd64
root@kali:~# modinfo 8812au
filename: /lib/modules/4.9.0-kali4-amd64/kernel/drivers/net/wireless/8812au.ko
version: v5.1.5_19247.20160830
author: Realtek Semiconductor Corp.
description: Realtek Wireless Lan Driver

root@kali:~# iwconfig wlan2
wlan2 IEEE 802.11 Mode:Monitor Frequency:2.467 GHz Tx-Power=12 dBm
Retry short limit:7 RTS thrff Fragment thrff
Power Managementff

root@kali:~# airmon-ng

PHY Interface Driver Chipset

phy0 wlan0 ath9k Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01)
phy1 wlan1 8812au Realtek Semiconductor Corp.
phy2 wlan2 8812au Realtek Semiconductor Corp.


root@kali:~# aireplay-ng -9 wlan2
22:50:41 Trying broadcast probe requests...
22:50:43 No Answer...
22:50:43 Found 1 AP

22:50:43 Trying directed probe requests...
22:50:43 00:B0:C0:02:35:7E - channel: 6 - 'Wireless3G'
22:50:43 Ping (min/avg/max): 2.305ms/3.134ms/5.721ms Power: -34.33
22:50:43 30/30: 100%

22:50:43 Injection is working!

dmesg:
[ 1671.481224] usb 1-5: new high-speed USB device number 3 using ehci-pci
[ 1671.630277] usb 1-5: New USB device found, idVendor=0bda, idProduct=a811
[ 1671.630281] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1671.630284] usb 1-5: Product: 802.11ac WLAN Adapter
[ 1671.630286] usb 1-5: Manufacturer: Realtek
[ 1671.630288] usb 1-5: SerialNumber: 00e04c000001
[ 1673.704810] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 1673.868128] usbcore: registered new interface driver 8812au
[ 1673.880117] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready

[Mister_X]

modprobe: ERROR: could not insert '8812au': Exec format error

That sounds like it was compiled with a different compiler than what was used to compile the kernel.

[dmatrix]

you are right Mister_X,
Check the version if it is the same:

root@kali:~# cat /proc/version
Linux version 4.9.0-kali4-amd64 ([email protected]) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2kali1 (2017-06-22)

root@kali:~# gcc --version
gcc (Debian 6.3.0-18) 6.3.0 20170516
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

See that both are 6.3.0 here.
If it is different, check and install if does not exist

apt-get install gcc-x
ls -l /usr/bin/gcc*
cd /usr/bin
rm gcc
ln -s gcc-x gcc

Compile again

[user55661]

still not working on a VM or regular Kali laptop :/ gcc is also verified as 6.3

UPDATE:
I am now getting this in dmesg but it's still not showing up in iwconfig

[ 61.455557] 8812au: loading out-of-tree module taints kernel.
[ 61.462934] RTL871X: module init start
[ 61.462935] RTL871X: 8812au v4.3.21_17997.20160531
[ 61.462936] RTL871X: build time: Jul 17 2017 14:08:06
[ 61.463901] usbcore: registered new interface driver 8812au
[ 61.463902] RTL871X: module init ret=0


so it seems like it should be working?? it just isn't appearing and it returns no errors running modprobe and restarting the network-manager does nothing

[dmatrix]

try compile version 5.1.5:
https://github.com/astsam/rtl8812au/tree/v5.1.5

not forget uninstall old version.

[Hercule]

Hi Guys,

Ive tried all of the above but i still cant get it to work, I dont know why. I get this error :

root@hercule:~# sudo apt install linux-headers-amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-amd64 is already the newest version (4.9+80+kali1).
0 upgraded, 0 newly installed, 0 to remove and 72 not upgraded.
root@hercule:~# sudo apt install realtek-rtl88xxau-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
realtek-rtl88xxau-dkms is already the newest version (4.3.21~20170330-0kali1).
0 upgraded, 0 newly installed, 0 to remove and 72 not upgraded.
root@hercule:~# sudo modprobe 8812au
modprobe: FATAL: Module 8812au not found in directory /lib/modules/4.9.0-kali3-amd64
root@hercule:~# sudo systemctl restart network-manager
root@hercule:~# uname -r
4.9.0-kali3-amd64
root@hercule:~# modinfo 8812au
modinfo: ERROR: Module 8812au not found.

PLEASE HELP ME!

EDIT:
Hi guys, thx for your i found the solution to my problem. So the problem was the headers. I uddated it doing an:

apt-get dist-upgrade

then uninstalled the drivers: apt-get remove realtek-rtl88xxau-dkms
apt-get purge realtek-rtl88xxau-dkms

and reinstalled them: apt-get install realtek-rtl88xxau-dkms

and then rebooted.

[krahsh]

root@kali:~# apt-get purge realtek-rtl88xxau-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'realtek-rtl88xxau-dkms' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@kali:~# apt-get install realtek-rtl88xxau-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
realtek-rtl88xxau-dkms
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,753 kB of archives.
After this operation, 18.2 MB of additional disk space will be used.
Selecting previously unselected package realtek-rtl88xxau-dkms.
(Reading database ... 271446 files and directories currently installed.)
Preparing to unpack .../realtek-rtl88xxau-dkms_5.1.5~20170828-0kali1_all.deb ...
Unpacking realtek-rtl88xxau-dkms (5.1.5~20170828-0kali1) ...
Setting up realtek-rtl88xxau-dkms (5.1.5~20170828-0kali1) ...
Loading new realtek-rtl88xxau-5.1.5~20170828 DKMS files...
It is likely that 4.4.50-v7 belongs to a chroot's host
Building for 4.4.50-v7
Building initial module for 4.4.50-v7
Error! Bad return status for module build on kernel: 4.4.50-v7 (armv7l)
Consult /var/lib/dkms/realtek-rtl88xxau/5.1.5~20170828/build/make.log for more information.

root@kali:~# cat /var/lib/dkms/realtek-rtl88xxau/5.1.5~20170828/build/make.log
DKMS make.log for realtek-rtl88xxau-5.1.5~20170828 for kernel 4.4.50-v7 (armv7l)
Sat Sep 16 00:47:40 UTC 2017
make ARCH=armv7l CROSS_COMPILE= -C /lib/modules/4.4.50-v7/build M=/var/lib/dkms/realtek-rtl88xxau/5.1.5~20170828/build modules
make[1]: Entering directory '/usr/src/kernel'
Makefile:617: arch/armv7l/Makefile: No such file or directory
make[1]: *** No rule to make target 'arch/armv7l/Makefile'. Stop.
make[1]: Leaving directory '/usr/src/kernel'
Makefile:1857: recipe for target 'modules' failed
make: *** [modules] Error 2

Not sure what to do next...

[username_placeholder]

try compile version 5.1.5:
https://github.com/astsam/rtl8812au/tree/v5.1.5

not forget uninstall old version.

Would

apt-get install realtek-rtl88xxau-dkms

work?

[BQAndroid]

Here's what I did to get the Alfa AWUS036ACH working on a dedicated Kali machine:
- Download Kali 2017.1 (you can download it via torrent).
- Burn it on a usb stick or cd and boot your laptop with it.
- Install Kali 2017.1
- After installation do the following:
- apt-get update && apt-get upgrade
- reboot
- apt install linux-headers-$(uname -r)
- apt install realtek-rtl88xxau-dkms
- plug in your Alfa AWUS036ACH.
- Now do a ifconfig and you will see that wlan1 is listed (wlan0 is the card in your laptop).
- if you want to use the aircrack suite do this:
- airmon-ng check kill
- Then put your card in monitoring mode by doing this:
- ip link set wlan1 down
- iwconfig wlan1 mode monitor
- ip link set wlan1 up
- Do not use airmon-ng start wlan1 to get your card into mon mode because it will fail to do so.
- then do airodump-ng wlan1 to do a recon on 2.4 GHz APs
- verify if injection is working on 2.4 GHz: aireplay-ng -9 wlan1
- now do airodump-ng wlan1 --band a to do a recon on 5 GHz APs
- then do airodump-ng wlan1 --bssid <MAC of your own 5 GHz AP> --channel <channel of your own 5 GHz AP>
- be patient for a minute or so and give airodump some time to do its work.
- Now do a aireplay-ng -9 wlan1 >>> if the result is 0 APs then it doesn't necessarily mean that injection isn't working.
- Do the following:
- aireplay-ng -0 10 -x 1024 -a <MAC of your own 5 GHz AP> -c <MAC of your connected device> wlan1 and check if your device gets disconnected.
- You may actually be lucky >>> device gets disconnected.
- Now do again a aireplay-ng -9 wlan1
- There may be a chance that aireplay says that injection is working!
- So give it a try!
- Note: aireplay doesn't always work well on 5 GHz, but MDK3 does a great job (in my kali VM aireplay's working nice though).

[Dilligaf1812]

I did everything listed. It keeps telling me “module build for kernel 4.9.0-Kali3-amd64 was skipped since the kernel headers for this kernel does not seem to be installed” any ideas?

UPDATE:
I have even resorted back to the drivers on the install disk but I’m not sure if I’m doing it right, from the disk. Something is up with Kali or maybe the Linux system it’s self. I’m wondering if the driver needs to be rewritten, or I’m just an unlucky SOB. Lol I’ll stay tuned to any updates. Thanks all

[Dilligaf1812]

_event_max_sample_rate to 49000
[17177.424838] 8812au: Unknown symbol __vfs_read (err 0)
[17651.149637] usb 4-5: new high-speed USB device number 4 using ehci-pci
[17651.306536] usb 4-5: New USB device found, idVendor=0bda, idProduct=8812
[17651.306539] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17651.306541] usb 4-5: Product: 802.11n NIC
[17651.306543] usb 4-5: Manufacturer: Realtek
[17651.306545] usb 4-5: SerialNumber: 123456
[17651.335769] 8812au: Unknown symbol __vfs_read (err 0)
[17651.368115] 8812au: Unknown symbol __vfs_read (err 0)
[18320.676952] 8812au: Unknown symbol __vfs_read (err 0)
[19440.281044] print_req_error: I/O error, dev fd0, sector 0
[19440.281050] floppy: error 10 while reading block 0
root@kali:~#
This is what Dmesg is telling me. For some reason it keeps telling me that the 8812au has an unknown symbol? Can anyone please interpret this for me. I have googled the **** out of it along with youtube, and still haven't a clue.

[Bu5h1d0]

_event_max_sample_rate to 49000
[17177.424838] 8812au: Unknown symbol __vfs_read (err 0)
[17651.149637] usb 4-5: new high-speed USB device number 4 using ehci-pci
[17651.306536] usb 4-5: New USB device found, idVendor=0bda, idProduct=8812
[17651.306539] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17651.306541] usb 4-5: Product: 802.11n NIC
[17651.306543] usb 4-5: Manufacturer: Realtek
[17651.306545] usb 4-5: SerialNumber: 123456
[17651.335769] 8812au: Unknown symbol __vfs_read (err 0)
[17651.368115] 8812au: Unknown symbol __vfs_read (err 0)
[18320.676952] 8812au: Unknown symbol __vfs_read (err 0)
[19440.281044] print_req_error: I/O error, dev fd0, sector 0
[19440.281050] floppy: error 10 while reading block 0
root@kali:~#
This is what Dmesg is telling me. For some reason it keeps telling me that the 8812au has an unknown symbol? Can anyone please interpret this for me. I have googled the **** out of it along with youtube, and still haven't a clue.

Pretty much same error is happening to me.
Anyone have a resolution for this?

[ 945.405736] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8812
[ 945.417369] 8812au: loading out-of-tree module taints kernel.
[ 945.418385] 8812au: Unknown symbol __vfs_read (err 0)
[ 945.438624] 8812au: Unknown symbol __vfs_read (err 0)

[MinorGlitch]

Pretty much same error is happening to me.
Anyone have a resolution for this?

[ 945.405736] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8812
[ 945.417369] 8812au: loading out-of-tree module taints kernel.
[ 945.418385] 8812au: Unknown symbol __vfs_read (err 0)
[ 945.438624] 8812au: Unknown symbol __vfs_read (err 0)

Same here. Getting super frustrated. Any ideas?


root@kali:~# dmesg | tail
[ 7.904120] work still pending
[ 17.284259] fuse init (API version 7.26)
[ 96.956239] usb 1-2: new high-speed USB device number 3 using xhci_hcd
[ 97.298158] usb 1-2: New USB device found, idVendor=0bda, idProduct=8812
[ 97.298159] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 97.298160] usb 1-2: Product: 802.11n NIC
[ 97.298161] usb 1-2: Manufacturer: Realtek
[ 97.298162] usb 1-2: SerialNumber: 123456
[ 97.334250] 8812au: Unknown symbol __vfs_read (err 0)
[ 97.337387] 8812au: Unknown symbol __vfs_read (err 0)

[re4son]

Patching of the 8812au is a bit like a merry-go-round
Kudos to kimocoder. He's found the magic ingredients this time and seems to have the most reliable driver for the latest kernels.
This is how I installed it:

git clone https://github.com/kimocoder/rtl8812au
cd rtl8812au
make && make install

ip link set wlan0 down
iwconfig wlan0 mode monitor
ip link set wlan0 up

airodump-ng -i wlan0

Everything seems to works like a treat - managed mode, monitor, etc. Rock solid so far.

Hope that helps.

[Bu5h1d0]

Patching of the 8812au is a bit like a merry-go-round
Kudos to kimocoder. He's found the magic ingredients this time and seems to have the most reliable driver for the latest kernels.
This is how I installed it:

git clone https://github.com/kimocoder/rtl8812au
cd rtl8812au
make && make install

ip link set wlan0 down
iwconfig wlan0 mode monitor
ip link set wlan0 up

airodump-ng -i wlan0

Everything seems to works like a treat - managed mode, monitor, etc. Rock solid so far.

Hope that helps.

Confirmed working, make sure you uninstall the older drivers first.
apt remove realtek-rtl88xxau-dkms && apt purge realtek-rtl88xxau-dkms
apt autoremove && apt autoclean
reboot now

Then follow what re4son posted.


Thanks for the update on their update re4son. ;0

[Dilligaf1812]

Thank you both for the awesome info, I finally have it up and running

[MinorGlitch]

Confirmed working, make sure you uninstall the older drivers first.
apt remove realtek-rtl88xxau-dkms && apt purge realtek-rtl88xxau-dkms
apt autoremove && apt autoclean
reboot now

Then follow what re4son posted.


Thanks for the update on their update re4son. ;0

MY GUYS! I have tried probably 100 different ways to fix this stupid thing. You guys are my heroes <3
Everything working flawlessly!
Cheers!

[crazar]

I have my alfa awus036ach showing in lsusb, but not ifconfig.

Didndt have any errors when installing. Any ideas? modprobe? or what?

[jkerr86]

tried set up as per kimocoder. installed from github and compiled, no wireless device detected, although it does show up in lsusb. might be a dud unit, as the light on it hasn't come on at all....

[DigiSolLabs]

I am not sure if you have been able to resolve this, but it seems that if you have updated the distribution, there seems to be an incompatibility between the kernel and the driver (the way it is installed). In the thread above, there seems to be an assumption that Kali 2017.1 this will work ...

Here's what I did to get the Alfa AWUS036ACH working on a dedicated Kali machine:
- Download Kali 2017.1 (you can download it via torrent).
- Burn it on a usb stick or cd and boot your laptop with it.
- Install Kali 2017.1

Well .... yes it will work! But with 2017.1 version. However, if you upgrade the distribution, it will stop working. It worked for me and it stopped once I moved to the latest distribution (currently running 2017.3) ... it just stopped working. I also got the same "8812au: Unknown symbol __vfs_read (err 0)" once I checked the dmesg info. Check what release you have and you may have to wait until this issue is resolved. Other than that, go back to the 2017.1 distribution and install it. That is certain to work ...

# cat /etc/*-release
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="2017.3"
VERSION_ID="2017.3"
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/"

I think it worked on 2017.2 as well (I think as I do an distribution upgrade often) ... but now it doesn't. I also remember doing everything suggested above from 2017.1 to 2017.2 ... removing, purging and re-installing. And that worked. I thought I would be doing the same thing ... but it did not work this time.

[DigiSolLabs]

Confirmed working, make sure you uninstall the older drivers first.
apt remove realtek-rtl88xxau-dkms && apt purge realtek-rtl88xxau-dkms
apt autoremove && apt autoclean
reboot now

Then follow what re4son posted.


Thanks for the update on their update re4son. ;0

This worked ... as after the dist-upgrade seemed to mess things up a bit with the driver. Thanks ... this should do it!

[Jparker171]

Patching of the 8812au is a bit like a merry-go-round
Kudos to kimocoder. He's found the magic ingredients this time and seems to have the most reliable driver for the latest kernels.
This is how I installed it:

git clone https://github.com/kimocoder/rtl8812au
cd rtl8812au
make && make install

ip link set wlan0 down
iwconfig wlan0 mode monitor
ip link set wlan0 up

airodump-ng -i wlan0

Everything seems to works like a treat - managed mode, monitor, etc. Rock solid so far.

Hope that helps.

I am unable to run the make and make install commands. I keep getting errors. I have uninstalled the old drivers and even attempted this on a fresh install of kali. please help.

/bin/sh: 1:bc not found
make -j 1 ARCH=i386 CROSS_COMPILE= -C /lib/modules/4.13.0-kalil-686-pae/build M=/root/rtl8812au modules
make[1]: *** /lib/modules/4.13.0-kalil-686-pae/build: No such file or directory.
stop.
Makefile:1871: recipe for target 'modules' failed
make: *** [modules] Error 2

[cowmooflage]

I am unable to run the make and make install commands. I keep getting errors. I have uninstalled the old drivers and even attempted this on a fresh install of kali. please help.

/bin/sh: 1:bc not found
make -j 1 ARCH=i386 CROSS_COMPILE= -C /lib/modules/4.13.0-kalil-686-pae/build M=/root/rtl8812au modules
make[1]: *** /lib/modules/4.13.0-kalil-686-pae/build: No such file or directory.
stop.
Makefile:1871: recipe for target 'modules' failed
make: *** [modules] Error 2

Hi,
having the same error here on Kali 2013.1 64bit from the VMWare fusion image. Having previously installed the driver, to no avail, I ran:

apt remove realtek-rtl88xxau-dkms && apt purge realtek-rtl88xxau-dkms
apt autoremove
apt autoclean

root@kali:~/repos/rtl8812au# make && make install
/bin/sh: 1: bc: not found
make -j 4 ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.13.0-kali1-amd64/build M=/root/repos/rtl8812au  modules
make[1]: *** /lib/modules/4.13.0-kali1-amd64/build: No such file or directory.  Stop.
Makefile:1871: recipe for target 'modules' failed
make: *** [modules] Error 2

Having created the missing folder, I get:

root@kali:~/repos/rtl8812au# make && make install
/bin/sh: 1: bc: not found
make -j 4 ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.13.0-kali1-amd64/build M=/root/repos/rtl8812au  modules
make[1]: Entering directory '/lib/modules/4.13.0-kali1-amd64/build'
make[1]: *** No rule to make target 'modules'.  Stop.
make[1]: Leaving directory '/lib/modules/4.13.0-kali1-amd64/build'
Makefile:1871: recipe for target 'modules' failed
make: *** [modules] Error 2

[re4son]

Looks like you both are missing the relevant kernel headers. Installing them should do the treat - and throw in "bc" for good measure :-)

apt update && apt install bc linux-headers-$(uname -r)

Hope that helps

[oxidat]

root@jb:~/rtl8812au# make
/bin/sh: 1: bc: not found
make -j 8 ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.14.0-kali1-amd64/build M=/root/rtl8812au modules
make[1]: *** /lib/modules/4.14.0-kali1-amd64/build: Datei oder Verzeichnis nicht gefunden. Schluss.
Makefile:1871: die Regel für Ziel „modules“ scheiterte
make: *** [modules] Fehler 2
root@jb:~/rtl8812au#


Use kali 17.3 and what is please flasch that I do not get to work?

[re4son]

Hi oxidat,

headers are missing (and bc). Just run this first:

apt update && apt install bc linux-headers-$(uname -r)

Hope that helps

[Trace]

Tried installing yesterday ... drivers install, monitor mode works but the adapter range is terrible ... funnily enough it improves if plugged into a usb2 port ???

Here's some more detail: https://forums.kali.org/showthread.p...nce-comparison

[cowmooflage]

Hi, after another apt update today I was finally able to have apt install linux-kernel-$(uname -r) succeed and the kimocoder driver finally compiled and installed with make && make install.

Now, as I plug in the NIC, the light turns on and it is visible to both ifconfig and iwconfig in managed mode by default, although with power management off (dunno if that's normal or not).

root@kali:~# iwconfig
wlan0     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=18 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

Unfortunately, trying to enable monitor mode with airmon-ng gives the following error message:

root@kali:~# airmon-ng check kill

Killing these processes:

  PID Name
  538 wpa_supplicant
  577 dhclient

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

I still seem to be able to set the card to monitor mode via iwconfig

root@kali:~# iwconfig wlan0 mode monitor
root@kali:~# iwconfig
wlan0     IEEE 802.11  Mode:Monitor  Frequency:2.412 GHz  Tx-Power=18 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          
eth0      no wireless extensions.

lo        no wireless extensions.

...but a following airodump-ng wlan0 only sees one access point while other, lower quality adapters in the house are able to see at least one more.

Can anyone help? Thanks in advance

[Trace]

Your only seeing one AP because the available current on your usb3 port is being restricted to 200ma by the driver and the adapter range is severely handicapped,

As discussed in the other AWUS036ACH thread: https://forums.kali.org/showthread.p...nce-comparison

Haven't got a solution yet unfortunately ...

[Apos]

Confirmed working, make sure you uninstall the older drivers first.
apt remove realtek-rtl88xxau-dkms && apt purge realtek-rtl88xxau-dkms
apt autoremove && apt autoclean
reboot now

Then follow what re4son posted.


Thanks for the update on their update re4son. ;0

Amazing! It worked! Thanks everyone involved!

[Black Creek]

Hi all,

this worked perfectly for me! I am so happy now :-)

i have the Alfa AWUS036ACH and a Realtek AR8812AU (2,4 and 5 GHz Wireless Adapter) and both are working now.

My System: Kali 2017.3 - upgraded today.

thanks to Bu5h1d0 and re4son!

Confirmed working, make sure you uninstall the older drivers first.
apt remove realtek-rtl88xxau-dkms && apt purge realtek-rtl88xxau-dkms
apt autoremove && apt autoclean
reboot now

Then follow what re4son posted.


Thanks for the update on their update re4son. ;0

[sandyx3]

I am unable to run the make and make install commands. I keep getting errors. I have uninstalled the old drivers and even attempted this on a fresh install of kali. please help.

/bin/sh: 1:bc not found
make -j 1 ARCH=i386 CROSS_COMPILE= -C /lib/modules/4.13.0-kalil-686-pae/build M=/root/rtl8812au modules
make[1]: *** /lib/modules/4.13.0-kalil-686-pae/build: No such file or directory.
stop.
Makefile:1871: recipe for target 'modules' failed
make: *** [modules] Error 2

I'm also receiving receiving the same errors when trying to do the make && make install commands. When I try installing the headers using apt update && apt install bc linux-headers-$(uname -r), I get the error that Unable to locate package linux-headers-4.13.0-kalil-amd64

[Trace]

I'm also receiving receiving the same errors when trying to do the make && make install commands. When I try installing the headers using apt update && apt install bc linux-headers-$(uname -r), I get the error that Unable to locate package linux-headers-4.13.0-kalil-amd64

Use the weekly build (4.14 kernel) from here and you won't get the unable to locate error: https://cdimage.kali.org/kali-images/kali-weekly/

[ab0kixxl]

Patching of the 8812au is a bit like a merry-go-round
Kudos to kimocoder. He's found the magic ingredients this time and seems to have the most reliable driver for the latest kernels.
This is how I installed it:

git clone https://github.com/kimocoder/rtl8812au
cd rtl8812au
make && make install

ip link set wlan0 down
iwconfig wlan0 mode monitor
ip link set wlan0 up

airodump-ng -i wlan0

Everything seems to works like a treat - managed mode, monitor, etc. Rock solid so far.

Hope that helps.

@re4son

I have been searching online for weeks how to get my Alfa adapter AWUS036ACH to work on my Kali 3.0 which i wasn't able to do with all the tutorials i found until i read through your post here....
and i think it might just work but not sure though...

I followed your instructions and i was able to get to the "make && make install" part...

I want to know if i would need to install this "install -p -m 644 8812au.ko /lib/modules/4.14.0-kali3-amd64/kernel/drivers/net/wireless/
/sbin/depmod -a 4.14.0-kali3-amd64" ?? (Help me out on how to continue from here) THANK YOU

This is the output below
root@ArchAngel:~/rtl8812au# make && make install
make -j 4 ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.14.0-kali3-amd64/build M=/root/rtl8812au modules
make[1]: Entering directory '/usr/src/linux-headers-4.14.0-kali3-amd64'
CC [M] /root/rtl8812au/core/rtw_cmd.o
CC [M] /root/rtl8812au/core/rtw_security.o
CC [M] /root/rtl8812au/core/rtw_debug.o
CC [M] /root/rtl8812au/core/rtw_io.o
CC [M] /root/rtl8812au/core/rtw_ioctl_query.o
CC [M] /root/rtl8812au/core/rtw_ioctl_set.o
CC [M] /root/rtl8812au/core/rtw_ieee80211.o
CC [M] /root/rtl8812au/core/rtw_mlme.o
CC [M] /root/rtl8812au/core/rtw_mlme_ext.o
CC [M] /root/rtl8812au/core/rtw_mi.o
CC [M] /root/rtl8812au/core/rtw_wlan_util.o
CC [M] /root/rtl8812au/core/rtw_vht.o
CC [M] /root/rtl8812au/core/rtw_pwrctrl.o
CC [M] /root/rtl8812au/core/rtw_rf.o
CC [M] /root/rtl8812au/core/rtw_recv.o
CC [M] /root/rtl8812au/core/rtw_sta_mgt.o
CC [M] /root/rtl8812au/core/rtw_ap.o
CC [M] /root/rtl8812au/core/rtw_xmit.o
CC [M] /root/rtl8812au/core/rtw_p2p.o
CC [M] /root/rtl8812au/core/rtw_tdls.o
CC [M] /root/rtl8812au/core/rtw_br_ext.o
CC [M] /root/rtl8812au/core/rtw_iol.o
CC [M] /root/rtl8812au/core/rtw_sreset.o
CC [M] /root/rtl8812au/core/rtw_btcoex.o
CC [M] /root/rtl8812au/core/rtw_beamforming.o
CC [M] /root/rtl8812au/core/rtw_odm.o
CC [M] /root/rtl8812au/core/efuse/rtw_efuse.o
CC [M] /root/rtl8812au/os_dep/osdep_service.o
CC [M] /root/rtl8812au/os_dep/linux/os_intfs.o
CC [M] /root/rtl8812au/os_dep/linux/usb_intf.o
CC [M] /root/rtl8812au/os_dep/linux/usb_ops_linux.o
CC [M] /root/rtl8812au/os_dep/linux/ioctl_linux.o
CC [M] /root/rtl8812au/os_dep/linux/xmit_linux.o
CC [M] /root/rtl8812au/os_dep/linux/mlme_linux.o
CC [M] /root/rtl8812au/os_dep/linux/recv_linux.o
CC [M] /root/rtl8812au/os_dep/linux/ioctl_cfg80211.o
CC [M] /root/rtl8812au/os_dep/linux/rtw_cfgvendor.o
CC [M] /root/rtl8812au/os_dep/linux/wifi_regd.o
CC [M] /root/rtl8812au/os_dep/linux/rtw_android.o
CC [M] /root/rtl8812au/os_dep/linux/rtw_radiotap.o
CC [M] /root/rtl8812au/os_dep/linux/rtw_proc.o
CC [M] /root/rtl8812au/os_dep/linux/ioctl_mp.o
CC [M] /root/rtl8812au/hal/hal_intf.o
CC [M] /root/rtl8812au/hal/hal_com.o
CC [M] /root/rtl8812au/hal/hal_com_phycfg.o
CC [M] /root/rtl8812au/hal/hal_phy.o
CC [M] /root/rtl8812au/hal/hal_dm.o
CC [M] /root/rtl8812au/hal/hal_btcoex.o
CC [M] /root/rtl8812au/hal/hal_mp.o
CC [M] /root/rtl8812au/hal/hal_mcc.o
CC [M] /root/rtl8812au/hal/hal_hci/hal_usb.o
CC [M] /root/rtl8812au/hal/led/hal_usb_led.o
CC [M] /root/rtl8812au/hal/HalPwrSeqCmd.o
CC [M] /root/rtl8812au/hal/rtl8812a/Hal8812PwrSeq.o
CC [M] /root/rtl8812au/hal/rtl8812a/Hal8821APwrSeq.o
CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_xmit.o
CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_sreset.o
CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_hal_init.o
CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_phycfg.o
CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_rf6052.o
CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_dm.o
CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_rxdesc.o
CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_cmd.o
CC [M] /root/rtl8812au/hal/rtl8812a/usb/usb_halinit.o
CC [M] /root/rtl8812au/hal/rtl8812a/usb/rtl8812au_led.o
CC [M] /root/rtl8812au/hal/rtl8812a/usb/rtl8812au_xmit.o
CC [M] /root/rtl8812au/hal/rtl8812a/usb/rtl8812au_recv.o
CC [M] /root/rtl8812au/hal/rtl8812a/usb/usb_ops_linux.o
CC [M] /root/rtl8812au/hal/efuse/rtl8812a/HalEfuseMask8812A_USB.o
CC [M] /root/rtl8812au/hal/efuse/rtl8812a/HalEfuseMask8821A_USB.o
CC [M] /root/rtl8812au/hal/rtl8812a/hal8812a_fw.o
CC [M] /root/rtl8812au/hal/rtl8812a/hal8821a_fw.o
CC [M] /root/rtl8812au/hal/phydm/phydm_debug.o
CC [M] /root/rtl8812au/hal/phydm/phydm_antdiv.o
CC [M] /root/rtl8812au/hal/phydm/phydm_antdect.o
CC [M] /root/rtl8812au/hal/phydm/phydm_interface.o
CC [M] /root/rtl8812au/hal/phydm/phydm_hwconfig.o
CC [M] /root/rtl8812au/hal/phydm/phydm.o
CC [M] /root/rtl8812au/hal/phydm/halphyrf_ce.o
CC [M] /root/rtl8812au/hal/phydm/phydm_edcaturbocheck.o
CC [M] /root/rtl8812au/hal/phydm/phydm_dig.o
CC [M] /root/rtl8812au/hal/phydm/phydm_pathdiv.o
CC [M] /root/rtl8812au/hal/phydm/phydm_rainfo.o
CC [M] /root/rtl8812au/hal/phydm/phydm_dynamicbbpowersaving.o
CC [M] /root/rtl8812au/hal/phydm/phydm_powertracking_ce.o
CC [M] /root/rtl8812au/hal/phydm/phydm_dynamictxpower.o
CC [M] /root/rtl8812au/hal/phydm/phydm_adaptivity.o
CC [M] /root/rtl8812au/hal/phydm/phydm_cfotracking.o
CC [M] /root/rtl8812au/hal/phydm/phydm_noisemonitor.o
CC [M] /root/rtl8812au/hal/phydm/phydm_acs.o
CC [M] /root/rtl8812au/hal/phydm/phydm_beamforming.o
CC [M] /root/rtl8812au/hal/phydm/phydm_dfs.o
CC [M] /root/rtl8812au/hal/phydm/txbf/halcomtxbf.o
CC [M] /root/rtl8812au/hal/phydm/txbf/haltxbfinterface.o
CC [M] /root/rtl8812au/hal/phydm/txbf/phydm_hal_txbf_api.o
CC [M] /root/rtl8812au/hal/phydm/phydm_kfree.o
CC [M] /root/rtl8812au/hal/phydm/phydm_ccx.o
CC [M] /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_fw.o
CC [M] /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_mac.o
CC [M] /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_bb.o
CC [M] /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_rf.o
CC [M] /root/rtl8812au/hal/phydm/rtl8812a/halphyrf_8812a_ce.o
CC [M] /root/rtl8812au/hal/phydm/rtl8812a/phydm_regconfig8812a.o
CC [M] /root/rtl8812au/hal/phydm/rtl8812a/phydm_rtl8812a.o
CC [M] /root/rtl8812au/hal/phydm/txbf/haltxbfjaguar.o
CC [M] /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_fw.o
CC [M] /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_mac.o
CC [M] /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_bb.o
CC [M] /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_rf.o
CC [M] /root/rtl8812au/hal/phydm/rtl8821a/halphyrf_8821a_ce.o
CC [M] /root/rtl8812au/hal/phydm/rtl8821a/phydm_regconfig8821a.o
CC [M] /root/rtl8812au/hal/phydm/rtl8821a/phydm_rtl8821a.o
CC [M] /root/rtl8812au/hal/phydm/rtl8821a/phydm_iqk_8821a_ce.o
CC [M] /root/rtl8812au/platform/platform_ops.o
CC [M] /root/rtl8812au/core/rtw_mp.o
LD [M] /root/rtl8812au/8812au.o
Building modules, stage 2.
MODPOST 1 modules
CC /root/rtl8812au/8812au.mod.o
LD [M] /root/rtl8812au/8812au.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.14.0-kali3-amd64'
install -p -m 644 8812au.ko /lib/modules/4.14.0-kali3-amd64/kernel/drivers/net/wireless/
/sbin/depmod -a 4.14.0-kali3-amd64

[re4son]

Hi ab0kixxl,

Congratulations, you should be ready to rock 'n roll :-)
Looks like you've compiled the module successfully (all lines down to the third from the bottom), and it was successfully installed (last two lines).

Just take it for a spin to test it out, e.g.:

ip link set wlan0 down
iwconfig wlan0 mode monitor
ip link set wlan0 up

airodump-ng -i wlan0

Happy hacking,
Re4son

[ab0kixxl]

@re4son

Hello there,please have you ever come across this type of issue with maltego in kali? i tried to run a scan with it but am not getting any outputs...this is what i get below when i run a scan with it..am using the community Maltego CE version..which has the latest version installed..

Am getting this output below when i try to scan with Maltego....it's not giving me any result..

Running transform To Files (Office) [using Search Engine] on 1 entities (from entity "shoppnow.ng")
Running transform To Emails @domain [using Search Engine] on 1 entities (from entity "shoppnow.ng")
Running transform To Email addresses [PGP] on 1 entities (from entity "shoppnow.ng")
Bing Transforms can only be used with paid versions of Maltego (from entity "shoppnow.ng")
Transform To Emails @domain [using Search Engine] returned with 0 entities (from entity "shoppnow.ng")
Transform To Emails @domain [using Search Engine] done (from entity "shoppnow.ng")
Bing Transforms can only be used with paid versions of Maltego (from entity "shoppnow.ng")
Transform To Files (Office) [using Search Engine] returned with 0 entities (from entity "shoppnow.ng")
Transform To Files (Office) [using Search Engine] done (from entity "shoppnow.ng")
Transform To Email addresses [PGP] returned with 0 entities (from entity "shoppnow.ng")
Transform To Email addresses [PGP] done (from entity "shoppnow.ng")

[re4son]

I just gave it a go with that domain and it seems to be working fine. These transforms usually never return much, that's all.

Have you used Maltego before? If not you might be in for little disappointment.
The free version is very restricted and even the paid one requires a lot of manual work, patience and tinkering (at least when I use it).

I used to use the paid version to get a quick initial overview of the Internet footprint of large organisations and I never just ran all transforms. I ran one transform, cleaned up the result and went on to the next one.


I'd get a free API key for the Passive Total transforms and run each of them manually for the domain before continuing down the tree of the results.


Hope that helps.

[Gen.Patten]

Coming in with quite the noobish question

I've been following re4son's instructions and all has been going well up until make && make install. At that point I come across this error:

make -j 4 ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.12.0-kali1-amd64/build M=/root/rtl8812au  modules
make[1]: *** /lib/modules/4.12.0-kali1-amd64/build: No such file or directory.  Stop.
Makefile:1871: recipe for target 'modules' failed
make: *** [modules] Error 2

I've got bc installed along with 4.14.0 headers. I've seen this error posted by others before but the /bin/sh: 1: bc: not found is not there anymore. Any ideas as to what I'm doing wrong?

[re4son]

It's looking for 4.12.0 headers and they seem to be missing.
Make sure that the running kernel matches the headers you installed. Could be as simple as rebooting after installing a new kernel and headers package.

[dk89]

I had no problems installing the driver (version 5.1.5 with apt-get). Unfortunately it is very slow and unusable and I cannot manage to find the problem. If I use my (very poor) internal WiFi I find around 50 networks within second. When I try the AWUSA36ACH most of the time there is no network found. If I'm lucky I see my own router. I can see the wifi card and I can switch to monitor mode:

root@kali:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
        inet6 fe80::a00:27ff:fe98:3178  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:98:31:78  txqueuelen 1000  (Ethernet)
        RX packets 6925  bytes 5107081 (4.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3866  bytes 528184 (515.8 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 1000  (Local Loopback)
        RX packets 20  bytes 1116 (1.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 20  bytes 1116 (1.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=867<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,ALLMULTI>  mtu 1500
        unspec 00-C0-CA-96-10-67-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 5  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 wlan0 mode monitor
root@kali:~# ip link set wlan0 down
root@kali:~# iwconfig wlan0 mode monitor
root@kali:~# ip link set wlan0 up
root@kali:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11  Mode:Monitor  Frequency:2.437 GHz  Tx-Power=18 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off

I tried it with Kali GNU/Linux Rolling with the 4.14.0 Kernel. I installed if within a VM and a persistent USB-Stick. Result was unfortunately the same. I also tried w USB 2 and a USB 3 Cable cause I read somewhere that might make difference but no success. You guys have any hints for me.

[Trace]

Hi dk89 ... it would appear this is quite a common problem with some hardware (including my own) ... I get terrible range from all drivers after 4.3.20.

Check out this page on github where we've been discussing it with some driver developers and leave your hardware details as it may help towards a solution:

https://github.com/aircrack-ng/rtl8812au/issues/77

Also try out the new 5.2.20 drivers (didn't work for me) and let us know how you get on:

https://github.com/kimocoder/rtl8812au-1