Package Details: rtl88xxau-aircrack-dkms-git r1164.b8167e6-1

Git Clone URL: https://aur.archlinux.org/rtl88xxau-aircrack-dkms-git.git (read-only, click to copy)
Package Base: rtl88xxau-aircrack-dkms-git
Description: Aircrack-ng kernel module for Realtek 88XXau (USB adapters only) network cards (8811au, 8812au and 8821au chipsets) with monitor mode and injection support
Upstream URL: https://github.com/aircrack-ng/rtl8812au
Keywords: 8811au 8812au 8821au aircrack dkms driver injection rtl8811au rtl8812au rtl8821au rtl88xx wireless
Licenses: GPL
Conflicts: rtl8812au-aircrack-dkms-git, rtl8812au-dkms-git, rtl8812au-inject-dkms-git, rtl8814au-dkms-git, rtl8821au-dkms-git
Submitter: iyanmv
Maintainer: iyanmv
Last Packager: iyanmv
Votes: 44
Popularity: 2.44
First Submitted: 2019-01-29 20:43
Last Updated: 2021-06-28 15:26

Dependencies (2)

Required by (0)

Sources (2)

Pinned Comments

iyanmv commented on 2020-11-10 17:40

8814au chipset support is turned off in this driver. Please use this package instead. Also, if you plan to use both packages at the same time, make sure that you have an up-to-date package.

iyanmv commented on 2020-01-10 16:02

This package now forces to use the branch v5.6.4.2 (the one that works better for me), which is the default one in the remote repository although they still mention branch v5.3.4 as the stable one. If you have any issues, please leave a comment, and also tried to change the branch in the source array. For example, change it to:

source=('rtl88xxau::git+https://github.com/aircrack-ng/rtl8812au.git#branch=v5.3.4'

Read the README.me to learn how to set your interface in monitor mode (and other things).

Important: Use ip and iw instead of ifconfig and iwconfig

Latest Comments

« First ‹ Previous ... 2 3 4 5 6 7 8 9 10 11 12 ... Next › Last »

iyanmv commented on 2020-02-02 23:10

@k96hkh this is a tricky question. To be honest, I do not know if this driver would work even in the case that your chipset supports that. But you can give it a try and figure it out. First, I would be sure that your device can simultaneously use both bands at the same time. iw list can help you find that out. Having two antennas doesn't mean that it can use both bands at the same time. Normally you can create as many software monitor interfaces as you want (iw dev YOUR_CHIPSET interface add NAME_MONITOR_INTERFACE type monitor), although with this driver I have issues with this thing, but they will compete for the resources, meaning that if you, for example use airodump-ng simultaneously with both interfaces on different channels, it will not work as you expected. There are some chipsets that support that though, but I guess you will have some lines in the "interface combinations" section when you run iw list.

What I usually do when I want to scan both 2.4 and 5 GHz bands is select the specific channels and let airodump-ng hop from one to another. It works quite good. For example, airodump-ng -WMU wlp0s20u1 -c 1,6,11,36,44

k96hkh commented on 2020-02-02 12:57

Thanks for a great work on this package! I have a question and maybe someone here knows or can point in the right direction. I have an USB external adapter with two antennas. Is it possible to create one AP at 2.4 GHz and and one at 5 GHz at the same time? What I have found on the internet is: Maybe if two interfaces are created for the adapter. Is this something rtl88xxau driver can do? Is it depending on adapter or maybe just "no can do".

Cheers!

iyanmv commented on 2020-02-01 21:07

@banzr not really, what if someone uses linux-lts, linux-hardened or linux-zen? Why would they want linux-headers on their system? I think people using dkms should take care of installing the headers they need. All these are mentioned as optional dependencies when installing dkms.

Anonymous comment on 2020-02-01 19:45

This package is missing a dependency to linux-headers.

mokkurkalve commented on 2020-01-12 11:29

Versions of this driver after r918.73f0a88 still completely knocks out my system as described below. https://aur.archlinux.org/packages/rtl88xxau-aircrack-dkms-git/#comment-716905 r918.73f0a88 still works fine.

iyanmv commented on 2020-01-10 16:02

This package now forces to use the branch v5.6.4.2 (the one that works better for me), which is the default one in the remote repository although they still mention branch v5.3.4 as the stable one. If you have any issues, please leave a comment, and also tried to change the branch in the source array. For example, change it to:

source=('rtl88xxau::git+https://github.com/aircrack-ng/rtl8812au.git#branch=v5.3.4'

Read the README.me to learn how to set your interface in monitor mode (and other things).

Important: Use ip and iw instead of ifconfig and iwconfig

iyanmv commented on 2020-01-07 22:13

@ayuksel this is rtl88xxau not rtl8814au

ayuksel commented on 2020-01-04 02:56

I am not sure how to log it or necessarily prove it, but I am on Manjaro with kernel 5.3. I am using the netgear A7000 with rtl8814au, and I am not having an issue with detection but for some reason the connection keeps randomly dropping on a very consistent basis. I had tried with this ubuntu and it had turned out fine with kernel 5.0, but now on Manjaro it is not working at all. Also, when the connection does drop my network manager still says I'm connected to the network, but it won't load anything and the traffic for both upload/download drop to 0.

trulex commented on 2019-11-19 20:02

Thanks

mokkurkalve commented on 2019-11-18 11:11

I have adapter Asus USB-AC56 (RTL8812AU). I use NetworkManager with IWD backend. Currently I've landed on using commit r918.73f0a88 for this driver, with the addition of cherrypicking commit https://github.com/aircrack-ng/rtl8812au/commit/55484785ccb2b6bdf7a8227f685092d7c67cb976.patch/ to turn off the enormous flow of debug messages that spammed my logs and rendered them utterly useless. This setup is working very well for me. I've also tried using the currently latest commit in the repo. But somewhere between r918.73f0a88 and r965.a8ec357 there's snuck in a commit that hangs my system; can't use shell, can't reboot by software, and I wouldn't know how to start debugging that with an unuseable system.