Alfa AWUS036ACH Kali Configuration Guide

[jzhyc5]

Excellent post. I wish there were more posts of such quality on the net, would have saved me a few hours of torture.

Shame Alpha can't be bothered to present their Linux install is such a concise, accurate manner

 

[Bigbiz]

Go into your windows network adpter menu and disable then enable the virtual machine network bridge. Also try to troubleshoot. 

[vp0023]

On 2/25/2018 at 8:36 PM, The Power Company said:

 

Like many others, I bought myself an Alfa AWUS036ACH, only to find its drivers are not set up by default on the latest version of Kali (despite many if its more recent reviews pointing out this fact). I found that there are few guides on how to get this sexy dual-band interface going, so I made a quick shell script to do everything in one shot. A few things to note before we begin:

1. You need an internet connection for this to work
2. This script works great on a fresh installation of the latest version of Kali Linux (2018.1). I tried running the script on a live boot, but the kernel yelled at me when I was modprobe-ing. If you want this to work with live boot, you will probably need to set up persistence or a custom image. Neither of those options are that difficult.
3. Some of the commands towards the end are not necessary for installation, but I used them while I was figuring out how to set everything up, so I left them in there in case anything breaks.
4. If you are anything like me, you may have a few broken drivers polluting your /usr/src folder from previous failed attempts. Delete them before attempting.
5. Once script has run, I recommend you add the following lines to your NetworkManager.conf

[keyfile]
unmanaged-devices=interface-name:wlan1;interface-name:wlan2

This prevents NetworkManager from trying to resolve the interface using its own stuff when you reboot again (real men keep NetworkManager disabled anyway, but whatever). If your PC already has a wlan0 assigned by default (i.e. is a laptop with built-in wifi),  the keyfile above should work fine. Otherwise, just add interface-name:wlan0; before interface-name:wlan1; The reason I also disabled a second, nonexistent wlan2 at the end is because sometimes, if I unplug the interface and replug it into a different USB port, it will be assigned one number up. This measure adds one get-out-of-NetworkManager-free card to your hand, increasing your chance to pass go and collect that sweet $200.

       6. Once you have gotten the interface set up, I would recommend using ifconfig to put it into monitor mode, instead of airmon-ng. I've found that airmon-ng tends to have issues with manually installed drivers on occasion. In case you don't know, here is how its done (assuming your Alfa is assigned wlan1):

ifconfig wlan1 down
iwconfig wlan1 mode monitor
ifconfig wlan1 up

Anyway, here is the script in question. As you probably already know, you can copy it to a text file called coolfilename.sh, set it to executable, and give that baby a run from the terminal. Or you could always just manually run the following commands one at a time.

#!/bin/sh

# Shell script to set up drivers for Alfa AWUS036ACH
# You must have an internet connection.

# update your repositories
apt-get update

# install dkms if it isn't already
apt-get install dkms

# change directory to /usr/src
cd /usr/src

# if you have any other drivers installed,remove them like so:
rm -r rtl8812AU-4.3.22/

# get latest driver from github
# used to be: git clone https://github.com/aircrack-ng/rtl8812au
git clone https://github.com/gordboy/rtl8812au.git

# move into downloaded driver folder
cd rtl8812au/

# update files in working tree to match files in the index 
# this step doesn't seem to be necessary anymore, commented out
# git checkout --track remotes/origin/v5.2.20

# make drivers
make

# move into parent directory
cd ..

# debugging
dkms status

# rename file for use with dkms
mv rtl8812au/ rtl8812au-5.2.20

# dkms add driver
dkms add -m rtl8812au -v 5.2.20 

# build drivers
dkms build -m rtl8812au -v 5.2.20

# install drivers
dkms install -m rtl8812au -v 5.2.20

# debugging
lsmod

# summon new interface from the depths of the kernel
modprobe 8812au

# wifi interface should now appear.
ip link

 

EDIT 10-17-2018

As per the driver's Github page, added the following line to dkms build steps: dkms add -m rtl8812au -v 5.2.20

Script was successful for Debian, should now work again for any Debian-based linux distro.

I ran the script , followed everything in here, but when I do a "sudo iwconfig wlx00c0caaaddae mode monitor" I get "Error for wireless request "Set Mode" (8B06) :    SET failed on device wlx00c0caaaddae ; Invalid argument." I have a Alfa AWUS036ACH with me. I am using Ubuntu 18.04. I have been trying many guides nothing worked. Can someone help me ?

Also my dmesg ouput is as follows:

[181017.002982] RTL871X: module init start
[181017.002983] RTL871X: rtl8812au v4.3.8_12175.20140902
[181017.002983] RTL871X: build time: Feb 13 2020 13:50:26
[181024.441485] RTL871X: rtw_ndev_init(wlan0)
[181024.441907] usbcore: registered new interface driver rtl8812au
[181024.441908] RTL871X: module init ret=0
[181024.449625] rtl8812au 1-3:1.0 wlx00c0caaaddae: renamed from wlan0
[181024.493856] IPv6: ADDRCONF(NETDEV_UP): wlx00c0caaaddae: link is not ready
[181033.287490] IPv6: ADDRCONF(NETDEV_UP): wlx00c0caaaddae: link is not ready
[181033.346290] IPv6: ADDRCONF(NETDEV_UP): wlx00c0caaaddae: link is not ready
[185952.127441] IPv6: ADDRCONF(NETDEV_UP): wlx00c0caaaddae: link is not ready
[187209.712522] IPv6: ADDRCONF(NETDEV_UP): wlx00c0caaaddae: link is not ready
[187474.984402] IPv6: ADDRCONF(NETDEV_UP): wlx00c0caaaddae: link is not ready
[187884.608642] IPv6: ADDRCONF(NETDEV_UP): wlx00c0caaaddae: link is not ready
[189477.265227] IPv6: ADDRCONF(NETDEV_UP): wlx00c0caaaddae: link is not ready
[191487.250794] IPv6: ADDRCONF(NETDEV_UP): wlx00c0caaaddae: link is not ready
[191960.915444] IPv6: ADDRCONF(NETDEV_UP): wlx00c0caaaddae: link is not ready

 

[vp0023]

16 hours ago, kdodge said:

there is one thing I would recommend you try, just to try and see if its a hardware or software problem. Load Kali/Parrot/Linux on a liveusb and boot up to that and try to use the wifi adapter outside of VirtualBox. VirtualBox's usb doesn't always work as expected, and if it works easily with the liveusb then it's probably a problem with VirtualBox. It's a rather easy step to try when troubleshooting.

I am not using a VirtualBox, I am using a physical machine with Ubuntu 18.04.

[Nagesh Singh]

thank you very much i can not express how i am feeling after overcoming this issue, it worked well for me , thank you very much.