The aircrack-ng version does not entirely work for me (although I have a workaround). On startup, I have a netctl profile called "home" that should bring up the network, but when I use the aircrack-ng driver, it fails with "WPA association/authentication failed for interface 'wlan0'". This driver (rtl8821au-dkms-git) does not have the same problem: the netctl profile brings up the network without any problems.
In the aircrack-ng case, I can eventually get the network up and running with the following workaround, though I don't yet know why this works: 1. sudo ip link set wlan0 up 2. sudo netctl start home (step 2 fails because it sees that the interface is already up, but the workaround doesn't work without it) 3. sudo ip link set wlan0 down 4. sudo netctl start home
For some reason that sequence of commands eventually brings the network up, so my guess is that there's something that the "ip" tool is doing to initialize my adapter that the aircrack-ng driver is not.
For what it's worth, the USB ID for my adapter is 0bda:0811. The product itself is the NET-DYN AC600 USB Wi-Fi Adpater: https://netdynwifi.com/product/ac600-usb-wi-fi-adapter/ .
I can run some tests if anyone would like more information, but unfortunately I don't have much time to investigate this myself.
Pinned Comments
zebulon commented on 2019-10-01 06:18 (UTC)
To all having an issue with this driver: please try https://aur.archlinux.org/packages/rtl88xxau-aircrack-dkms-git alternatively.
solsticedhiver commented on 2019-03-17 10:59 (UTC) (edited on 2019-03-17 21:10 (UTC) by solsticedhiver)
a patch to make it work for rpi and may be other ARM device:
Note: I am seeing the interface of the usb wifi key marketed as DEEPOW dongle (from amazon) changing MAC address at every boot even though I have not set up anything like that in netctl, here.
I don't know if it's a hardware problem or driver problem. However, it's the same with rtl88xxau-aircrack-dkms-git driver