Target Devices
Adapters with chipset: RTL8811AU, RTL8821AU, RTL8812AU, RTL8814AU
| Chipset | Vendor | Model |
|---|---|---|
| RTL8811AU | ALFA Network | AWUS036ACS |
| RTL8821AU | To be added | To be added |
| RTL8812AU | ALFA Network | AWUS036AC |
| ALFA Network | AWUS036ACH | |
| ALFA Network | AWUS036EAC | |
| RTL8814AU | ALFA Network | AWPCIE-1900U |
| ALFA Network | AWUS1900 |
Driver Information
Developed internally by Realtek, and then patched by open community members.
This drivers is not mainlined (might never will be, from the look of it), so you’ll be loading a self-compiled out-of-tree kernel module. If you are running on a system using UEFI Secure Boot, you may need to either disable Secure Boot or sign the kernel module before you can load it. (We won’t cover that here.)
To check the status of Secure Boot, run
|
1 |
mokutil --sb-state |
Output will be one of the following:
SecureBoot enabled— using UEFI, Secure Boot enabledSecureBoot disabled— using UEFI, Secure Boot disabledEFI variables are not supported on this system— not using UEFI, Secure Boot disabled
Driver Installation
Kali Linux
For those who are running Kali Linux ARM Image on Raspberry Pi, the driver should be installed already.
For x86 users, installed package realtek-rtl88xxau-dkms.
|
1 2 |
sudo apt update sudo apt install realtek-rtl88xxau-dkms |
Parrot OS
Security edition has package realtek-rtl88xxau-dkms installed by default. If this is not the case, follow the same instructions above for Kali Linux.
Debian and Its Derivatives (on x86, x86_64 Platforms)
Debian, Ubuntu, Linux Mint, elementary OS, etc.
APT is able to install local deb file since version 1.1 — we can use that to install realtek-rtl88xxau-dkms from Kali.
First, find the latest realtek-rtl88xxau-dkms deb package from Kali’s repository.
At the time of writing/updating, the latest one is realtek-rtl88xxau-dkms_5.6.4.2~20200529-0kali1_all.deb.
|
1 2 3 |
wget https://http.kali.org/kali/pool/contrib/r/realtek-rtl88xxau-dkms/realtek-rtl88xxau-dkms_5.6.4.2~20200529-0kali1_all.deb sudo apt update sudo apt install ./realtek-rtl88xxau-dkms_5.6.4.2~20200529-0kali1_all.deb |
Although not tested, some distros should be able to perform the whole process in GUI — download deb package through browser and double-click to install.
Fedora
|
1 |
sudo dnf install dkms kernel-devel make |
Note that because the kernel module is built with DKMS you should ensure you have installed and rebooted to latest kernel update before installing.
|
1 2 3 |
git clone -b v5.6.4.2 https://github.com/aircrack-ng/rtl8812au.git cd rtl* sudo ./dkms-install.sh |
CentOS
|
1 2 |
sudo yum install epel-release sudo yum install git dkms kernel-devel make |
Note that because the kernel module is built with DKMS you should ensure you have installed and rebooted to latest kernel update before installing.
|
1 2 3 |
git clone -b v5.6.4.2 https://github.com/aircrack-ng/rtl8812au.git cd rtl* sudo ./dkms-install.sh |
Arch Linux
These instructions are expansions of
|
1 |
sudo pacman -Syu --needed base-devel git dkms linux-headers |
If you’re not using the default kernel, package linux-headers should be changed respectively. Say you’re using LTS kernel, the command would then be
|
1 |
sudo pacman -Syu --needed base-devel git dkms linux-lts-headers |
Note that because the kernel module is built with DKMS you should ensure you have installed and rebooted to latest kernel update before installing.
|
1 2 3 |
git clone https://aur.archlinux.org/rtl88xxau-aircrack-dkms-git.git cd rtl88xxau-aircrack-dkms-git makepkg -si |
Appendixes
Getting package URI
In case that repository URL changes in the future, spin up a Kali VM or even a Docker container, and run
|
1 2 |
sudo apt update apt download --print-uris realtek-rtl88xxau-dkms |
Monitor, Injection Support
May not work on distros other than Kali, which is specifically tweaked for pentesting.
4 Comments for “Realtek 802.11ac USB Wi-Fi Linux Driver Installation”
Tilo
says:Hi,
on pi with kernel I got, any suggestions?
pi@raspberrypi:~ $ sudo apt install ./realtek-rtl88xxau-dkms_5.3.4~20200115-0kali1_all.deb
Reading package lists… Done
Building dependency tree
Reading state information… Done
Note, selecting ‘realtek-rtl88xxau-dkms’ instead of ‘./realtek-rtl88xxau-dkms_5.3.4~20200115-0kali1_all.deb’
realtek-rtl88xxau-dkms is already the newest version (5.3.4~20200115-0kali1).
0 upgraded, 0 newly installed, 0 to remove and 86 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up realtek-rtl88xxau-dkms (5.3.4~20200115-0kali1) …
Removing old realtek-rtl88xxau-5.3.4~20200115 DKMS files…
——————————
Deleting module version: 5.3.4~20200115
completely from the DKMS tree.
——————————
Done.
Loading new realtek-rtl88xxau-5.3.4~20200115 DKMS files…
It is likely that 4.19.75+ belongs to a chroot’s host
Building for 4.19.75+, 4.19.75-v7+, 4.19.75-v7l+ and 4.19.75-v8+
Building initial module for 4.19.75+
Error! Bad return status for module build on kernel: 4.19.75+ (armv6l)
Consult /var/lib/dkms/realtek-rtl88xxau/5.3.4~20200115/build/make.log for more information.
dpkg: error processing package realtek-rtl88xxau-dkms (–configure):
installed realtek-rtl88xxau-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
realtek-rtl88xxau-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
Kuan-Yi Li
says:Raspberry Pi has a different architecture (ARM, not x86 or x86_64). The easiest way is to use Kali Linux ARM Image, which has the driver built-in. Otherwise, you may have to follow compile instructions for Raspberry Pi and manually compile the driver from source.
Neftali
says:Hi, I installed the drivers on Ubuntu/Debian based distros but the USB wifi adapter does not automatically connect to Wifi on reboot. I also have to reconnect to my network but it saves as a new connection each time. Any suggestions?
Kuan-Yi Li
says:This is most likely not driver related but connection or interface name manager setting related. Connection profile usually includes some properties that specify the name or MAC address of interface it matches to, and also whether it is going to automatically connect. Thus I’m guessing either interface name manager somehow didn’t name that interface the same across reboot (did you plug the adapter to a different physical port?), or the connection profile wasn’t written properly.