aircrack-ng / rtl8812au Goto Github PK

Hi,

as you know, AC mode seems not to be working for some versions of the driver. In some cases, that you are not having an AC connection is pretty evident based on the link speed. But I have been unable to really figure out how to see the negotiated rate with the AP. In some other drivers, this information can be retrieved by the iw link command as shown below:

~ » iw dev wlan0 link
Connected to xx:xx (on wlan0)
	SSID: xxx
	freq: 5300
	RX: 239354305 bytes (268745 packets)
	TX: 38976845 bytes (145393 packets)
	signal: -60 dBm
	tx bitrate: 173.3 MBit/s VHT-MCS 8 short GI VHT-NSS 2

	bss flags:	short-slot-time
	dtim period:	1
	beacon int:	100

Unfortunately, for this driver, the information available is far less detailed:

~ » iw dev wlx00 link
Connected to xx:xx (on wlx00)
	SSID: xxx
	freq: 5300
	signal: -45 dBm
	tx bitrate: 216.7 MBit/s

Can we add the negotiated rate to the output of the iw link command? I assume that the command is retrieving the information from the kernel (and, therefore, the driver).

This will help us to do some testing in relation to AC support in the driver.

Thanks

Regards

root@javier-f22:/temp# ifconfig wlx00c0ca960c26 down
root@javier-f22:/temp# iwconfig wlx00c0ca960c26 mode monitor
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlx00c0ca960c26 ; Invalid argument.

The things I did is simply installing driver from this repository.

What could be wrong?

root@kali:# cd rtl8812au/
root@kali:/rtl8812au# make RTL8814=1
/bin/sh: 1: bc: not found
make -j 4 ARCH=i386 CROSS_COMPILE= -C /lib/modules/4.14.0-kali1-686-pae/build M=/root/rtl8812au modules
make[1]: se entra en el directorio '/usr/src/linux-headers-4.14.0-kali1-686-pae'
/bin/sh: 1: bc: not found
Building modules, stage 2.
/bin/sh: 1: bc: not found
MODPOST 1 modules
make[1]: se sale del directorio '/usr/src/linux-headers-4.14.0-kali1-686-pae'

A user is reporting that the "AWUS036ACH" is underpowered running at 200mA instead of 500mA

"I have noticed that with the Alfa AWUS036ACH device plugged in to a USB 3.0 port, it only is able to receive 200mA of power. When plugged into a USB 2.0 port it is able to receive 500mA. I'm not sure why this is, but the result of the loss in power is that the device has a very limited range for transmit and receive using these drivers. This information was obtained via the command lsusb -v."

"The AWUS036H being referenced in that post uses the RTL8187 driver, and runs at a full 500mA. The range on that adapter is much greater than the range on the AWUS036ACH, which uses the RTL8812AU driver. None of the users involved in this discovery are developers, so I'm adding this note here in hopes someone who knows what might fix this issue will see it."

Other sources:
https://forums.kali.org/showthread.php?38574-Old-AWUS036H-vs-new-AWUS036ACH-performance-comparison
abperiasamy/rtl8812AU_8821AU_linux#12

• Remove Windows support / code / parameters
• Remove code related to other than 8812 / 8814 chipsets (WORK IN PROGRESS)
• Fix sparse errors several places (WORK IN PROGRESS)

I installed your driver 4.3.21, it works perfect for the first time when i put it in the monitor mode then sent DeAuth to my target devices. My target devices was disconnect from my wifi. But i couldn't get any handshakes. The second time, i couldn't get anything from the airodump-ng

Update the readme to "make install RTL8814=1" not "make install 8814au"

I could not get v5.1.5 working with Wireless-AC. It would only connect at 5ghz N. Also the previous version 4.3.21 did have AC working. Is it possible to be able to use an earlier kernel so that v4.3.21 compiles

Things I have tried:
running apt-get update
then apt-get dist-upgrade.
reinstalled Kali 2017.1
reinstalled Kali rolling W37.

In my kali（4.14 kernel） vmware，I install v5.1.5 driver for 8812au ，it can find 2.4G network ，but can't find 5G, however in win10 it can find the 5G network! How can I deal with this problem?

do you plan to update this branch as it was done here is https://github.com/gordboy/rtl8812au ?

When i try to make from https://github.com/aircrack-ng/rtl8812au i get an error:
Make Rtl8814a :
/bin/sh: 1: syntax error: "(" unexpected
Makefile:1264: recipe for target 'modules' failed

Can be repeated, for example:
Ubuntu 16.04 LTS x86_64

1. wget https://cdn.kernel.org/pub/linux/kernel/v3.x/linux-3.16.51.tar.xz
2. tar -xJvpf linux-3.16.51.tar.xz
3. cd linux-3.16.51
4. make defconfig
5. make allmodconfig
6. make all
7. cd ..
8. wget https://github.com/astsam/rtl8812au/archive/v5.1.5.zip
9. 7z x v5.1.5.zip
10. cd rtl8812au-5.1.5
11. make KVER=3.16.51 KSRC=../linux-3.16.51
    astam is ok, but alternate
12. rm v5.1.5.zip; rm -rf rtl8812au-5.1.5
13. https://github.com/aircrack-ng/rtl8812au/archive/v5.1.5.zip
    or wget https://github.com/kimocoder/rtl8812au/archive/v5.1.5.zip
14. 7z x v5.1.5.zip
15. cd rtl8812au-5.1.5
16. make KVER=3.16.51 KSRC=../linux-3.16.51
    aircrack-ng or kimocoder compile bad, this error, same under arm and kernel 3.10 what I know

rtl8812au-5.1.5/os_dep/linux/ioctl_cfg80211.c: In function ‘cfg80211_rtw_get_station’:
rtl8812au-5.1.5/os_dep/linux/ioctl_cfg80211.c:1754:31: error: ‘STATION_INFO_BSS_PARAM_SHORT_PREAMBLE’ undeclared (first use in this function)
sinfo->bss_param.flags |= STATION_INFO_BSS_PARAM_SHORT_PREAMBLE;
^
rtl8812au-5.1.5/os_dep/linux/ioctl_cfg80211.c:1754:31: note: each undeclared identifier is reported only once for each function it appears in
rtl8812au-5.1.5/os_dep/linux/ioctl_cfg80211.c:1757:31: error: ‘STATION_INFO_BSS_PARAM_SHORT_SLOT_TIME’ undeclared (first use in this function)
sinfo->bss_param.flags |= STATION_INFO_BSS_PARAM_SHORT_SLOT_TIME;
^
rtl8812au-5.1.5/os_dep/linux/ioctl_cfg80211.c:1761:31: error: ‘STATION_INFO_BSS_PARAM_CTS_PROT’ undeclared (first use in this function)
sinfo->bss_param.flags |= STATION_INFO_BSS_PARAM_CTS_PROT;
^
rtl8812au-5.1.5/os_dep/linux/ioctl_cfg80211.c:1764:29: error: ‘STATION_INFO_BSS_PARAM_DTIM_PERIOD’ undeclared (first use in this function)
sinfo->bss_param.flags |= STATION_INFO_BSS_PARAM_DTIM_PERIOD;
^
CC [M] rtl8812au-5.1.5/os_dep/linux/wifi_regd.o
rtl8812au-5.1.5/os_dep/linux/ioctl_cfg80211.c: At top level:

I do not know the following setting mean. However, I have compile without error when set it to "y".

###################### MP HW TX MODE FOR VHT #######################
CONFIG_MP_VHT_HW_TX_MODE = n

Can anyone explain what that mean?

airodump-ng wlx00c0ca9623d0 crashes with:

read failed: Network is down
Interface wlx00c0ca9623d0: 
ioctl(SIOCGIFINDEX) failed: No such device
Can't reopen wlx00c0ca9623d0

This happens from time to time. Attached is the output of journactl --system -l -a with the crash and one output aborted by Ctrl+C. The relevant part seems to be:

Dec 18 16:28:12 debian kernel: RTW: reg 0x454, usb read 1 fail, status:-71 value=0x3ce0000, vendorreq_times:1
Dec 18 16:28:12 debian kernel: RTW: reg 0x454, usb read 1 fail, status:-71 value=0x3ce0000, vendorreq_times:2
Dec 18 16:28:12 debian kernel: RTW: reg 0x454, usb read 1 fail, status:-71 value=0x3ce0000, vendorreq_times:3
Dec 18 16:28:12 debian kernel: RTW: reg 0x454, usb read 1 fail, status:-71 value=0x3ce0000, vendorreq_times:4
Dec 18 16:28:12 debian kernel: RTW: reg 0x454, usb read 1 fail, status:-71 value=0x3ce0000, vendorreq_times:5
Dec 18 16:28:12 debian kernel: RTW: [dvobj:ffff9ceb97fe9000][ERROR] continual_io_error:5 > 4
Dec 18 16:28:12 debian kernel: usb 2-1: USB disconnect, device number 31

aborted-by-user.log.txt
crash.log.txt

Debian Stretch, 4.13 Backports Kernel (Linux debian 4.13.0-0.bpo.1-amd64 #1 SMP Debian 4.13.13-1~bpo9+1 (2017-11-22) x86_64 GNU/Linux, up to date rtl8812 git repository.
My /etc/NetworkManager/NetworkManager.conf looks like:

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

[keyfile]
unmanaged-devices=mac:00:c0:ca:96:23:d0

[device]
wifi.scan-rand-mac-address=no

Setbitrate with iw is not supported.
# iw wlanX set bitrates legacy-5 ht-mcs-5 vht-mcs-5 2:9

Some inspiration: initial ath10k implementation and current ath10k implementation

Using Kali 2017.1 updated to v4.12.0-kali1-amd64 kernel. Running as guest on VMWare Fusion 8.5.8, hosted on Mac OS X 10.12.6

To summarize: after installing the realtek-rtl-88xxau-dkms package, Kali ends up crashing (no exception), either:

• Instantly if the adapter is connected to an AP and, let's say a browser, is launched (or any other app generating traffic to the Internet): firefox don't even have the time to parse and display all the html/css code and the crash occurs before getting the full page displayed.

• Somehow after a several minutes if using the adapter otherwise: So, to gather more data, I chose this way of crashing Kali with Alfa AWUS036ACH and reproduced this incident by going into monitor mode and back to managed mode and connecting to my usual AP, disconnecting and returning to monitor mode, back and forth 2 or 3 times, before it did crash. (ip link set wlan0 down, iwconfig wlan0 mode monitor, ip link set wlan0 up, airodump-ng wlan0, ip link set wlan0 down, iwconfig wlan0 mode managed, ip link set wlan0 up, , , ip link set wlan0 down... and so forth...). Some other times I tried with using airman-ng check kill and/or stopping/starting/restarting network-manager at the relevant moments, with systemctl, but it does not change the outcome at all.

• Eventually within an hour, even if not plugging the Alfa adapter at all (actually, the only way not to end up crashing at some point has been for me te revert to the snapshot made right before installing the realtek-rtl88xxau-dkms package, and I have no issues of any kind thereafter).

The hereby documented crash occurred between 18:52:30 and 18:52:59 (I can't tell exactly, but all logs stop at 18:52:30). I rebooted at 21:51:00, and I am enclosing extracts from /var/log/:, (stamped from any recorded event occurring right prior to 18:52, to the time of reboot 21:51)

• daemon.log
• debug
• kern.log
• messages
• syslog
• user.log
  As well as screen captures:
• rtl88xxau-dkms-install, showing proper install of latest version of the package
• boot screenshot after crash showing after the necessary hard reboot.
• screenshot with modules related to rtl8812u's info

As a sanity-check, I tried and got exactly the same behavior with a fresh install of Kali 2017.1.

I hope this helps. Obviously, this is academically very interesting, but definitely not urgent in any way (besides, AWUS036NHA is still doing a great job!).

logs.zip

The Asus USB-AC68 works fine with this driver, but the phy is configured by default in 3Tx3Rx mode and the driver will only capture up to 3-stream traffic. I've tried module options (rtw_rf_config=1, rtw_rf_config=7) as well as a few tweaks to the driver but I have not been able to get this to capture 4 streams.

Has any one been successful at capturing 4-stream traffic with this card and driver?

Build fails as follows under 4.15-rc3 on Gentoo.

ethan@ethan-desktop ~/build/rtl8812au $ KVER=4.15.0-rc3 make RTL8814=1
make -j 12 ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.15.0-rc3/build M=/home/ethan/build/rtl8812au  modules
make[1]: Entering directory '/usr/src/linux-4.15-rc3'
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_cmd.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_security.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_debug.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_io.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_ioctl_query.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_ioctl_set.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_ieee80211.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_mlme.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_mlme_ext.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_mi.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_wlan_util.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_vht.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_pwrctrl.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_rf.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_recv.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_sta_mgt.o
  CC [M]  /home/ethan/build/rtl8812au/core/rtw_ap.o
In file included from ./include/linux/kernel.h:10:0,
                 from ./include/linux/list.h:9,
                 from ./include/linux/module.h:9,
                 from /home/ethan/build/rtl8812au/include/basic_types.h:81,
                 from /home/ethan/build/rtl8812au/include/drv_types.h:31,
                 from /home/ethan/build/rtl8812au/core/rtw_pwrctrl.c:22:
/home/ethan/build/rtl8812au/core/rtw_pwrctrl.c: In function ‘pwr_state_check_handler’:
./include/linux/kernel.h:930:51: error: ‘_adapter {aka struct _ADAPTER}’ has no member named ‘pwrctrlpriv’
  BUILD_BUG_ON_MSG(!__same_type(*(ptr), ((type *)0)->member) && \
                                                   ^
./include/linux/compiler.h:301:19: note: in definition of macro ‘__compiletime_assert’
   bool __cond = !(condition);    \
                   ^~~~~~~~~
./include/linux/compiler.h:324:2: note: in expansion of macro ‘_compiletime_assert’
  _compiletime_assert(condition, msg, __compiletime_assert_, __LINE__)
  ^~~~~~~~~~~~~~~~~~~
./include/linux/build_bug.h:47:37: note: in expansion of macro ‘compiletime_assert’
 #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
                                     ^~~~~~~~~~~~~~~~~~
./include/linux/kernel.h:930:2: note: in expansion of macro ‘BUILD_BUG_ON_MSG’
  BUILD_BUG_ON_MSG(!__same_type(*(ptr), ((type *)0)->member) && \
  ^~~~~~~~~~~~~~~~
./include/linux/kernel.h:930:20: note: in expansion of macro ‘__same_type’
  BUILD_BUG_ON_MSG(!__same_type(*(ptr), ((type *)0)->member) && \
                    ^~~~~~~~~~~
./include/linux/timer.h:144:2: note: in expansion of macro ‘container_of’
  container_of(callback_timer, typeof(*var), timer_fieldname)
  ^~~~~~~~~~~~
/home/ethan/build/rtl8812au/core/rtw_pwrctrl.c:403:23: note: in expansion of macro ‘from_timer’
  _adapter *padapter = from_timer(padapter, t, pwrctrlpriv.pwr_state_check_timer);
                       ^~~~~~~~~~
In file included from ./include/linux/compiler_types.h:58:0,
                 from ./include/uapi/linux/stddef.h:2,
                 from ./include/linux/stddef.h:5,
                 from ./include/uapi/linux/posix_types.h:5,
                 from ./include/uapi/linux/types.h:14,
                 from ./include/linux/types.h:6,
                 from /home/ethan/build/rtl8812au/include/basic_types.h:80,
                 from /home/ethan/build/rtl8812au/include/drv_types.h:31,
                 from /home/ethan/build/rtl8812au/core/rtw_pwrctrl.c:22:
./include/linux/compiler-gcc.h:166:2: error: ‘_adapter {aka struct _ADAPTER}’ has no member named ‘pwrctrlpriv’
  __builtin_offsetof(a, b)
  ^
./include/linux/stddef.h:17:32: note: in expansion of macro ‘__compiler_offsetof’
 #define offsetof(TYPE, MEMBER) __compiler_offsetof(TYPE, MEMBER)
                                ^~~~~~~~~~~~~~~~~~~
./include/linux/kernel.h:933:21: note: in expansion of macro ‘offsetof’
  ((type *)(__mptr - offsetof(type, member))); })
                     ^~~~~~~~
./include/linux/timer.h:144:2: note: in expansion of macro ‘container_of’
  container_of(callback_timer, typeof(*var), timer_fieldname)
  ^~~~~~~~~~~~
/home/ethan/build/rtl8812au/core/rtw_pwrctrl.c:403:23: note: in expansion of macro ‘from_timer’
  _adapter *padapter = from_timer(padapter, t, pwrctrlpriv.pwr_state_check_timer);
                       ^~~~~~~~~~
make[2]: *** [scripts/Makefile.build:310: /home/ethan/build/rtl8812au/core/rtw_pwrctrl.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1502: _module_/home/ethan/build/rtl8812au] Error 2
make[1]: Leaving directory '/usr/src/linux-4.15-rc3'
make: *** [Makefile:1871: modules] Error 2

Attempting build again a couple times without cleaning also reveals this from parallel jobs:

make[2]: *** Waiting for unfinished jobs....
/home/ethan/build/rtl8812au/os_dep/linux/mlme_linux.c:64:6: error: conflicting types for ‘rtw_join_timeout_handler’
 void rtw_join_timeout_handler(void *FunctionContext)
      ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/ethan/build/rtl8812au/include/drv_types.h:97:0,
                 from /home/ethan/build/rtl8812au/os_dep/linux/mlme_linux.c:23:
/home/ethan/build/rtl8812au/include/rtw_mlme.h:775:6: note: previous declaration of ‘rtw_join_timeout_handler’ was here
 void rtw_join_timeout_handler(struct timer_list *t);
      ^~~~~~~~~~~~~~~~~~~~~~~~
/home/ethan/build/rtl8812au/os_dep/linux/mlme_linux.c:70:6: error: conflicting types for ‘_rtw_scan_timeout_handler’
 void _rtw_scan_timeout_handler(void *FunctionContext)
      ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/ethan/build/rtl8812au/include/drv_types.h:97:0,
                 from /home/ethan/build/rtl8812au/os_dep/linux/mlme_linux.c:23:
/home/ethan/build/rtl8812au/include/rtw_mlme.h:776:6: note: previous declaration of ‘_rtw_scan_timeout_handler’ was here
 void _rtw_scan_timeout_handler(struct timer_list *t);
      ^~~~~~~~~~~~~~~~~~~~~~~~~
/home/ethan/build/rtl8812au/os_dep/linux/mlme_linux.c: In function ‘rtw_init_mlme_timer’:
/home/ethan/build/rtl8812au/os_dep/linux/mlme_linux.c:106:2: error: implicit declaration of function ‘_init_timer’; did you mean ‘__init_timer’? [-Werror=implicit-function-declaration]
  _init_timer(&(pmlmepriv->assoc_timer), padapter->pnetdev, rtw_join_timeout_handler, padapter);
  ^~~~~~~~~~~
  __init_timer
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:310: /home/ethan/build/rtl8812au/os_dep/linux/mlme_linux.o] Error 1
/home/ethan/build/rtl8812au/os_dep/linux/os_intfs.c: In function ‘devobj_init’:
/home/ethan/build/rtl8812au/os_dep/linux/os_intfs.c:1737:2: error: implicit declaration of function ‘_init_timer’; did you mean ‘__init_timer’? [-Werror=implicit-function-declaration]
  _init_timer(&(pdvobj->dynamic_chk_timer), NULL, _dynamic_check_timer_handlder, pdvobj);
  ^~~~~~~~~~~
  __init_timer

If there's anything else you need, let me know.

kernel v4.12 support is needed as Kali just pushed a v4.12 kernel in repos.

A kernel support patch may be seen here but i simply don't have the time these next days.

apparently there are problems with connectivity with virtual machines no matter if it is vmware or virtualbox in both there is problem, the antenna simply does not detect Wi-Fi networks and can not be used even when it is connected to the virtual machine, it has not been able to discover which is the real problem, but a possible solution that I found is the following; dial automatic connection of our alpha antenna to the virtual machine, turn off the computer and turn it back on and turn on our virtual machine the antenna can be connected to wifi networks, however there is another problem, the mondo monitor is very slow and the injection of packages I also leave print imprecations to show more what we do

Main problem in virtual machines occurs equally in vmware and in virtualbox

mark automatic connection of the device to the virtual machine, then turn off and restart the PC

in both virtual machines the automatic connection is activated

Once the previous thing is done, you have to force the antenna to the monitor mode in the following way because no wifi test application is able to put it automatically, the bad thing is that all the networks of our vm will fall even the eth0, and to top it all. antenna is slow in scanning, detects very few networks and does not inject packets correctly

a diference of another antenna that I have old driver rtl8187L

then I do not know if it is possible some kind of optimization or update that is able to correct this that I am presented and that surely more than one will be happening

I tried to use DWA192 USB dongle, based on 8814au chipset, with driver 5.1.5.
I seems that the driver sets FCS flag in radiotap header even though FCS is not present.
I also tried to capture on DWA182 (rtl8812au, same driver) and the problem doesn't appear, FCS tag is set and FCS is there.

I am using Kali Linux 2017.3 with latest update. My rtl8812au cannot connect to the router that is set to "required" for Protected Management Frames (IEEE 802.11w).

I have checked the source code and it is enabled when compile.

Hi,
I am using a TPLink Archer T9UH AC1900 card (RTL8814AU) with a Debian running a 4.13.4-2 kernel and v5.1.5 for this rtl8812au driver fork.
After setting the card into monitor mode it receives Management and Data packets and I also saw some MIMO packets with an MCS up to 11.

I noticed that there are no ACKs show in wireshark so I filtered for FC type 0 packets in the pcap file.
It is strange since my card is not receiving any Control packets in monitor mode.

Is this also the case with other RTL8814AU based cards?

Driver v5.2.20.2 is released. for 8812au at the moment.
More information found here

A complete changelog may be found here

I've started the work on this! Currently, frame injection (packet injection) has been added and is reported working, but there is lots to do on it still. Progress will be posted below.

Feel free to tag along, all contributions are welcome to make this a good driver.

I have a AWUS1900 connected to my raspberry pi (rtl8814 chipset).
Using the v4.3.21 branch the adapter picks up local wifis when running the latest kismet (the one with the webgui). After switching to v5.1.5 the wifi adapter works when spinnung up networks, but kismet does not show any found networks.
Is this a known limitation of the v5.1.5 branch?

The MAC address of the USB dongle (rtl8812au) is keeping change on every plugin.

Does this driver support virtual interface as most of the wifi tools need this feature to work properly?

I was using DWA-182 rev C1 (rtl8812au chipset) earlier this week and it was working fine with those drivers. I reinstalled my Kali and I was able to successfully install the drivers but i cannot see it in ifconfig. I hope you will be able to help me.

lsusb :

root@kali:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 2001:3315 D-Link Corp.  **(My adapter)**
Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 005: ID 0e0f:0008 VMware, Inc. 
Bus 001 Device 004: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 001 Device 002: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

dmesg :

[  344.362376] usb 1-2.1: new high-speed USB device number 8 using xhci_hcd
[  344.466782] usb 1-2.1: New USB device found, idVendor=2001, idProduct=3315
[  344.466786] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  344.466788] usb 1-2.1: Product: D-Link Wireless Adapter
[  344.466789] usb 1-2.1: Manufacturer: Realtek
[  344.466791] usb 1-2.1: SerialNumber: 123456

ifconfig :

root@kali:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet IP_HERE  netmask 255.255.255.0  broadcast IP_HERE
        inet6 IP_HERE  prefixlen 64  scopeid 0x20<link>
        ether MAC_HERE  txqueuelen 1000  (Ethernet)
        RX packets 67  bytes 8217 (8.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 194  bytes 15968 (15.5 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 32  bytes 1752 (1.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 32  bytes 1752 (1.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I use TP-link Archer T4U AC1300. Before installing driver, the adapter was detected(I mean that I can see the Deviceid of it after run the command "lsusb")but, after installing the driver, the id quickly disappeared.
But the driver worked few days ago, but now it didn't work. When the driver worked before, I just tried to inject frame, capture packets, and change the txpower to 30. It seemed that everything was OK except changing txpower.
I tried to install some different version of driver, but failed...

I'm sorry for my poor English, and thank you for reading.

Leaving a commit here for later savings.
The code will use a fixed mac address when one is not specified.

Would people be interested in this? pros vs cons?

goncalossilva/rtl8812AU@eaa89bf

Thanks.

Greetings,

my AC1200 adapter is stuck in USB2 mode and completely ignores any txpower setting.

I am running Linux Mint 18.2 with a 4.11.0-14 kernel.
I have tried the 5.1.5 and 5.2.9 version of the rtl8812au dkms module.
From the debug info I can not see any specific part that points to the module trying to switch the device over to USB3. Version 4.3.21 seems to work fine.

Appart from the txpower and the usb setting the adapter works. I can enter monitor mode and injection works as well as long as I stick to the 2.4 GHz band. However the range is severely limited with 12 dBm txpower and I get the feeling this has something to do with the adapter not being able to enter USB3 mode.

I will attach the debug messages, if I can provide any further info I would be happy to do so.

`
RTW: module init start
RTW: 8812au v5.1.5_19247.20160830
RTW: build time: Oct 19 2017 02:02:09
RTW: usb_endpoint_descriptor(0):
RTW: bLength=7
RTW: bDescriptorType=5
RTW: bEndpointAddress=81
RTW: wMaxPacketSize=512
RTW: bInterval=0
RTW: RT_usb_endpoint_is_bulk_in = 1
RTW: usb_endpoint_descriptor(1):
RTW: bLength=7
RTW: bDescriptorType=5
RTW: bEndpointAddress=2
RTW: wMaxPacketSize=512
RTW: bInterval=0
RTW: RT_usb_endpoint_is_bulk_out = 2
RTW: usb_endpoint_descriptor(2):
RTW: bLength=7
RTW: bDescriptorType=5
RTW: bEndpointAddress=3
RTW: wMaxPacketSize=512
RTW: bInterval=0
RTW: RT_usb_endpoint_is_bulk_out = 3
RTW: usb_endpoint_descriptor(3):
RTW: bLength=7
RTW: bDescriptorType=5
RTW: bEndpointAddress=4
RTW: wMaxPacketSize=512
RTW: bInterval=0
RTW: RT_usb_endpoint_is_bulk_out = 4
RTW: usb_endpoint_descriptor(4):
RTW: bLength=7
RTW: bDescriptorType=5
RTW: bEndpointAddress=85
RTW: wMaxPacketSize=64
RTW: bInterval=1
RTW: RT_usb_endpoint_is_int_in = 5, Interval = 1
RTW: nr_endpoint=5, in_num=2, out_num=3

RTW: USB_SPEED_HIGH
RTW: CHIP TYPE: RTL8812
RTW: read_chip_version_8812a SYS_CFG(0xF0)=0x04411137
RTW: rtw_hal_config_rftype RF_Type is 2 TotalTxPath is 2
RTW: Chip Version Info: CHIP_8812_Normal_Chip_TSMC_C_CUT_2T2R_RomVer(0)
RTW: _ConfigChipOutEP_8812 OutEpQueueSel(0x07), OutEpNumber(3)
RTW: Boot from EFUSE, Autoload OK !
lxMAC: CTRL-EVENT-SCAN-FAILED ret=-19 retry=1
RTW: HW EFUSE
RTW: eFuse Content:
(lots of stuff)
RTW: EEPROM ID=0x8129
RTW: VID = 0x0BDA, PID = 0x8812
RTW: Customer ID: 0x00, SubCustomer ID: 0xCD
RTW: EEPROMRegulatory = 0x0
RTW: Board Type: 0x 0
RTW: hal_com_config_channel_plan chplan:0x7F
RTW: CrystalCap: 0x1c
RTW: ThermalMeter = 0x20
RTW: Hal_ReadRemoteWakeup_8812A...bSupportRemoteWakeup(0)
RTW: pHalData->PAType_2G is 0x33, pHalData->ExternalPA_2G = 1
RTW: pHalData->PAType_5G is 0x33, pHalData->ExternalPA_5G = 1
RTW: pHalData->LNAType_2G is 0x88, pHalData->ExternalLNA_2G = 1
RTW: pHalData->LNAType_5G is 0x88, pHalData->ExternalLNA_5G = 1
RTW: pHalData->TypeGPA = 0x0
RTW: pHalData->TypeAPA = 0x0
RTW: pHalData->TypeGLNA = 0x0
RTW: pHalData->TypeALNA = 0x0
RTW: RFE Type: 0x 3
RTW: Usb Switch: 1
RTW: PID= 0x8812, VID= bda
RTW: PID= 0x8812, VID= bda
RTW: Customer ID: 0x 0
RTW: hal_ReadUsbType_8812AU: antenna=2, wmode=3
RTW: hal_ReadUsbType_8812AU(): EFUSE_HIDDEN_812AU
RTW: rtw_hal_read_chip_info in 128 ms
RTW: init_channel_set((null)) ChannelPlan ID:0x7f, ch num:37
RTW: NR_RECVBUFF: 8
RTW: MAX_RECVBUF_SZ: 32768
RTW: NR_PREALLOC_RECV_SKB: 8
RTW: rtw_alloc_macid((null)) if1, hwaddr:ff:ff:ff:ff:ff:ff macid:1
RTW: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1
RTW: phy_ConfigBBWithPgParaFile(): No File PHY_REG_PG.txt, Load from HWImg Array!
RTW: default power by rate loaded
RTW: can't get autopm:
RTW: rtw_macaddr_cfg mac addr:00:c0:ca:95:e8:a9
RTW: bDriverStopped:True, bSurpriseRemoved:False, bup:0, hw_init_completed:0
RTW: rtw_wiphy_alloc(phy19)
RTW: rtw_wdev_alloc(padapter=ffff9cdb81fd5000)
RTW: rtw_wiphy_register(phy19)
RTW: Register RTW cfg80211 vendor cmd(0x67) interface
RTW: rtw_ndev_init(wlan0) if1 mac_addr=00:c0:ca:95:e8:a9
RTW: rtw_ndev_notifier_call(wlan0) state:16
RTW: cfg80211_rtw_get_txpower
RTW: rtw_ndev_notifier_call(wlan0) state:5
usbcore: registered new interface driver 8812au
RTW: module init ret=0
RTW: cfg80211_rtw_get_txpower
`

going for a iwconfig device txpower 20 results in:
RTW: cfg80211_rtw_set_txpower
and nothing happens.

cheers

I can confirm that this driver doesn't compile on 4.14 kernel after kali linux dist-upgrade 2017.3

Also on kernel 4.13 it compiles and runs but with glitches (sometimes networks are not shown, packet injection is sluggish and after a while everything breaks and needs to be rebooted and sometimes reinstalled to get proper results.

The txpower goes upto 40dbm (which I haven't checked if that corresponds to the actual txpower)

If you need further testing on anything particular please let me know

here is compilation error on my notebook with debian and 4.11 kernel
can you fix it ?

CC [M] /var/lib/dkms/rtl8812au/5.1.5/build/os_dep/linux/ioctl_cfg80211.o
/var/lib/dkms/rtl8812au/5.1.5/build/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_cfg80211_add_monitor_if’:
/var/lib/dkms/rtl8812au/5.1.5/build/os_dep/linux/ioctl_cfg80211.c:3735:10: error: ‘struct net_device’ has no member named ‘priv_destructor’; did you mean ‘destructor’?
mon_ndev->priv_destructor = rtw_ndev_destructor;
^~
/usr/src/linux-headers-4.11.0-trunk-common/scripts/Makefile.build:299: ошибка выполнения рецепта для цели «/var/lib/dkms/rtl8812au/5.1.5/build/os_dep/linux/ioctl_cfg80211.o»
make[4]: *** [/var/lib/dkms/rtl8812au/5.1.5/build/os_dep/linux/ioctl_cfg80211.o] Ошибка 1
/usr/src/linux-headers-4.11.0-trunk-common/Makefile:1509: ошибка выполнения рецепта для цели «module/var/lib/dkms/rtl8812au/5.1.5/build»
make[3]: *** [module/var/lib/dkms/rtl8812au/5.1.5/build] Ошибка 2
Makefile:152: ошибка выполнения рецепта для цели «sub-make»
make[2]: *** [sub-make] Ошибка 2
Makefile:8: ошибка выполнения рецепта для цели «all»
make[1]: *** [all] Ошибка 2
make[1]: выход из каталога «/usr/src/linux-headers-4.11.0-trunk-amd64»
Makefile:1869: ошибка выполнения рецепта для цели «modules»
make: *** [modules] Ошибка 2

Hi there i have build from source but there are already errors ....

Here's the output of dmesg | tail ...

[ 1970.027202] usb 1-2: Product: 802.11ac NIC
[ 1970.027205] usb 1-2: Manufacturer: Realtek
[ 1970.027207] usb 1-2: SerialNumber: 123456
[ 1970.056788] 8814au: disagrees about version of symbol module_layout
[ 2160.844891] perf: interrupt took too long (2542 > 2500), lowering kernel.perf_event_max_sample_rate to 78500
[ 2273.608517] 8814au: module_layout: kernel tainted.
[ 2273.611254] 8814au: Unknown symbol __vfs_read (err 0)
[ 3199.585208] perf: interrupt took too long (3235 > 3177), lowering kernel.perf_event_max_sample_rate to 61750
[ 3636.233407] 8814au: Unknown symbol __vfs_read (err 0)
[ 3664.285700] 8814au: Unknown symbol __vfs_read (err 0)

hope anyone can help me ...

thx so much!!

Hi there!
I just saw that you opened this repsository. Well done! Thanks 😺
I installed the master branch wihtout any problem (for 8112au chipset) and it was even looking to go better than with other recent kerenels.
Than i wanted to install branch 4.3.21 but i got this errors whith ioctl_cfg80211.o

/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_cfg80211_indicate_connect’:
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:807:6: error: passing argument 2 of ‘cfg80211_roamed’ from incompatible pointer type [-Werror=incompatible-pointer-types]
    , notify_channel
      ^~~~~~~~~~~~~~
In file included from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/include/osdep_service_linux.h:98:0,
                 from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/include/osdep_service.h:41,
                 from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/include/drv_types.h:32,
                 from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:22:
/usr/src/linux-headers-4.12.0-kali1-common/include/net/cfg80211.h:5435:6: note: expected ‘struct cfg80211_roam_info *’ but argument is of type ‘struct ieee80211_channel *’
 void cfg80211_roamed(struct net_device *dev, struct cfg80211_roam_info *info,
      ^~~~~~~~~~~~~~~
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:809:6: warning: passing argument 3 of ‘cfg80211_roamed’ makes integer from pointer without a cast [-Wint-conversion]
    , cur_network->network.MacAddress
      ^~~~~~~~~~~
In file included from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/include/osdep_service_linux.h:98:0,
                 from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/include/osdep_service.h:41,
                 from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/include/drv_types.h:32,
                 from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:22:
/usr/src/linux-headers-4.12.0-kali1-common/include/net/cfg80211.h:5435:6: note: expected ‘gfp_t {aka unsigned int}’ but argument is of type ‘unsigned char *’
 void cfg80211_roamed(struct net_device *dev, struct cfg80211_roam_info *info,
      ^~~~~~~~~~~~~~~
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:805:3: error: too many arguments to function ‘cfg80211_roamed’
   cfg80211_roamed(padapter->pnetdev
   ^~~~~~~~~~~~~~~
In file included from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/include/osdep_service_linux.h:98:0,
                 from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/include/osdep_service.h:41,
                 from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/include/drv_types.h:32,
                 from /home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:22:
/usr/src/linux-headers-4.12.0-kali1-common/include/net/cfg80211.h:5435:6: note: declared here
 void cfg80211_roamed(struct net_device *dev, struct cfg80211_roam_info *info,
      ^~~~~~~~~~~~~~~
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_cfg80211_add_monitor_if’:
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:3962:10: error: ‘struct net_device’ has no member named ‘destructor’; did you mean ‘priv_destructor’?
  mon_ndev->destructor = rtw_ndev_destructor;
          ^~
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_cfg80211_preinit_wiphy’:
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:6618:18: error: ‘WIPHY_FLAG_SUPPORTS_SCHED_SCAN’ undeclared (first use in this function)
  wiphy->flags |= WIPHY_FLAG_SUPPORTS_SCHED_SCAN;
                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:6618:18: note: each undeclared identifier is reported only once for each function it appears in
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c: At top level:
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:6651:25: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
  .change_virtual_intf = cfg80211_rtw_change_iface,
                         ^~~~~~~~~~~~~~~~~~~~~~~~~
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:6651:25: note: (near initialization for ‘rtw_cfg80211_ops.change_virtual_intf’)
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:6676:22: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
  .add_virtual_intf = cfg80211_rtw_add_virtual_intf,
                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.c:6676:22: note: (near initialization for ‘rtw_cfg80211_ops.add_virtual_intf’)
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.12.0-kali1-common/scripts/Makefile.build:307: fallo en las instrucciones para el objetivo '/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.o'
make[4]: *** [/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au/os_dep/linux/ioctl_cfg80211.o] Error 1
/usr/src/linux-headers-4.12.0-kali1-common/Makefile:1532: fallo en las instrucciones para el objetivo '_module_/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au'
make[3]: *** [_module_/home/kcdtv/GitHub/RTL88XXAU/driversbyaircrack/rtl8812au] Error 2
Makefile:152: fallo en las instrucciones para el objetivo 'sub-make'
make[2]: *** [sub-make] Error 2
Makefile:8: fallo en las instrucciones para el objetivo 'all'
make[1]: *** [all] Error 2
make[1]: se sale del directorio '/usr/src/linux-headers-4.12.0-kali1-amd64'
Makefile:1717: fallo en las instrucciones para el objetivo 'modules'
make: *** [modules] Error 2

Notice that compilation went fine with branch 5.1.5 (always with 8812au)
The issue only affects branch v 4.3.21

Currently using a ASUS USB-AC68 that contains rtl8814au chipset.
Installed rtl8814au drivers with no problems.
USB devices works perfectly. can connect to networks and be put into monitor mode.
Airodump scans never result in WPA handshakes. Longest scan 2 hours.

Has anyone else seen this issue with the rtl884au chipset?

Currently working on a VM of Kali 4.12 on a Mac

When using rtl8814au to deauth, there is no data display. The latest (github) aircrack-ng is patched for 5GHz band. However, rtl8812au does not has this problem.

Setting the control channel 40 (5200MHz) and a bandwith of 80Mhz with the center channel 42 (5210MHz)
# iw dev wlan1 set freq 5200 80 5210
results in (observe the 30MHz difference to the control channel)

root@kali:/usr/src/rtl8812au# iw dev wlan1 info
Interface wlan1
	ifindex 10
	wdev 0x700000001
	addr 00:c0:ca:96:23:d0
	type monitor
	wiphy 7
	channel 40 (5200 MHz), width: 80 MHz, center1: 5170 MHz
	txpower 18.00 dBm 

or

root@kali:/usr/src/rtl8812au# iw dev wlan1 set freq 5300 80 5290
root@kali:/usr/src/rtl8812au# iw dev wlan1 info
Interface wlan1
	ifindex 12
	wdev 0x900000001
	addr 00:c0:ca:96:23:d0
	type monitor
	wiphy 9
	channel 60 (5300 MHz), width: 80 MHz, center1: 5270 MHz
	txpower 18.00 dBm

this probably due to os_dep/linux/ioctl_cfg80211.c line 4422 (static int cfg80211_rtw_get_channel):

	case CHANNEL_WIDTH_80:
				RTW_INFO("%s width 80\n", __func__);
				width = NL80211_CHAN_WIDTH_80;
				if(offset==HAL_PRIME_CHNL_OFFSET_LOWER){
					center_freq = control_freq +30;
				}else{
					center_freq = control_freq -30;
				}

in core/rtw_wlan_util.c would be rtw_get_center_ch for finding the center channel for every control channel.

u8 rtw_get_center_ch(u8 channel, u8 chnl_bw, u8 chnl_offset)
{
        u8 center_ch = channel;

        if (chnl_bw == CHANNEL_WIDTH_80) {
                if (channel == 36 || channel == 40 || channel == 44 || channel == 48)
                        center_ch = 42;
                else if (channel == 52 || channel == 56 || channel == 60 || channel == 64)
                        center_ch = 58;
                else if (channel == 100 || channel == 104 || channel == 108 || channel == 112)
                        center_ch = 106;
                else if (channel == 116 || channel == 120 || channel == 124 || channel == 128)
                        center_ch = 122;
                else if (channel == 132 || channel == 136 || channel == 140 || channel == 144)
                        center_ch = 138;
                else if (channel == 149 || channel == 153 || channel == 157 || channel == 161)
                        center_ch = 155;
                else if (channel == 165 || channel == 169 || channel == 173 || channel == 177)
                        center_ch = 171;
                else if (channel <= 14)
                        center_ch = 7;
        } else if (chnl_bw == CHANNEL_WIDTH_40) {
                if (chnl_offset == HAL_PRIME_CHNL_OFFSET_LOWER)
                        center_ch = channel + 2;
                else
                        center_ch = channel - 2;
        } else if (chnl_bw == CHANNEL_WIDTH_20)
                center_ch = channel;
        else
                rtw_warn_on(1);

        return center_ch;
}

With the iwlwifi Intel wlan it works as it should.

What's the project license?
I found that https://github.com/diederikdehaas/rtl8812AU/ (currently abandoned) was using GPL-2.0 (https://github.com/diederikdehaas/rtl8812AU/blob/driver-4.3.20/LICENSE). Is this project based on that one? Could someone add a LICENSE file to the sources?

Thanks!

I have tried to do every step for the installation of this driver, but apparently for more than try to make the RTL8814 = 1, it does not work, just install the RTL8812AU, help how do I install the correct driver ?, also the apt command -get install realtek-rtl88xxau-dkms, I also did not work, if the wifi icon appears, but when looking for wifi networks it shows absolutely nothing

https://ibb.co/gurxaw

OS: Kali

I'm running an AP with NetworkManager, and wanted to increase the signal strength.
But increasing TXPower from 15 to 30 then 32 has made no difference.

Am I missing something?

Thanks

Hi,

as the title says, the Alfa stays in USB2 mode. I have tracked the problem to the code below. For whatever the reason (I have the impression that the EEPROMUsbSwitch variable is not properly initialized in the 8814 driver but I have not tested this thoroughly), EEPROMUsbSwitch is false and this stops the mode change. Commenting the two lines solves the problem.

Regards.

--- a/os_dep/linux/usb_intf.c
+++ b/os_dep/linux/usb_intf.c
@@ -649,15 +649,17 @@ static int usb_reprobe_switch_usb_mode(PADAPTER Adapter)
        u8 ret = _FALSE;
 
        /* efuse not allow driver to switch usb mode */
-       if (pHalData->EEPROMUsbSwitch == _FALSE)
-               goto exit;
+       //if (pHalData->EEPROMUsbSwitch == _FALSE)
+       //      goto exit;

There is no device name or chipset name when using lsusb command.

Channel keeps changing whenever I try to do anything which would need a specific channel. Tried with iwconfig, iw, using channel number and frequency too

I compiled with the latest commit ac5840e of v5.1.5 for my RTL8812AU dongle. Since I do not have USB3.0 port on my laptop, I cannot sure if the driver is working on USB3.0 or not. However, I am sure that txpower can be set. Meanwhile, the frequency can be switched automatically when it is targeted to the AP.

When I am going to get the handshake, there is no deauthenticate traffic. Therefore, I check with the "iw list wlan1" and notice that there is no "disassocate" and "deauthenticate" in the "Supported commands" section and there is a few supported commands only.

Any idea?

Trying to run ./dkms-install.sh and I am receiving errors that the directory does not exist. See attached screen shot.

I would appreciate your help.

Thx you,

Don't have time to add it myself, since I'm away for 3 weeks from today.
Kernel v4.15 support may (or will) be added, it all goes down to the timers (that have been moved).

A work on kernel v4.15 support (patch which needs edit to fit) may be seen/ported from here

lwfinger/rtl8812au@f7322f3

Hello,

I'm not able to make aerodump work with this USB dongle using rtl8814au from this repo.

I'm testing it on a Ubuntu 17.10, with kernel version 4.13.0.

Is this device supported? Is there something I can do?

Using Debian GNU/Linux Kernel 4.12.0-0.bpo.2-amd64 compiled version 4.3.21 from github.
Adapter AWSU036ACH (AC1200) using rtl8812au

Setting up an access point in 802.11n mode with hostapd works fine as far as I can see. Switching to ac mode however results in "Could not set channel for kernel driver".
I actually do not know whether this functionality is already part of this driver. I would be more than happy to offer additional information if requested or test patches.

Log output from hostapd:
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd.conf
ctrl_interface_group=0
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported vendor command: vendor_id=0x1018 subcmd=1
nl80211: Supported vendor command: vendor_id=0x1a11 subcmd=4106
nl80211: Supported vendor command: vendor_id=0x1a11 subcmd=4107
nl80211: Supported vendor event: vendor_id=0x1018 subcmd=0
nl80211: Supported vendor event: vendor_id=0x1018 subcmd=1
nl80211: interface wlan0 in phy phy1
nl80211: Set mode ifindex 15 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x55791746b2d0 (device SME)
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55791746b2d0 match=04
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55791746b2d0 match=0501
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55791746b2d0 match=0503
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55791746b2d0 match=0504
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55791746b2d0 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55791746b2d0 match=08
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55791746b2d0 match=09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55791746b2d0 match=0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55791746b2d0 match=11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x55791746b2d0 match=7f
nl80211: Enable Probe Request reporting nl_preq=0x55791746c960
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0x55791746c960 match=
rfkill: initial event: idx=1 type=1 op=0 soft=0 hard=0
nl80211: Add own interface ifindex 23 (ifidx_reason 15)
nl80211: if_indices[16]: 23(15)
nl80211: Add own interface ifindex 15 (ifidx_reason -1)
nl80211: if_indices[16]: 23(15) 15(-1)
nl80211: Adding interface wlan0 into bridge br0
phy: phy1
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code DE, new country code DE
nl80211: Regulatory information - country=DE (DFS-ETSI)
nl80211: 2400-2483 @ 40 MHz 20 mBm
nl80211: 5150-5250 @ 80 MHz 20 mBm (no outdoor)
nl80211: 5250-5350 @ 80 MHz 20 mBm (no outdoor) (DFS)
nl80211: 5470-5725 @ 160 MHz 26 mBm (DFS)
nl80211: 5725-5875 @ 80 MHz 13 mBm
nl80211: 57000-66000 @ 2160 MHz 40 mBm
nl80211: Added 802.11b mode based on 802.11g information
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=12 freq=2467 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=13 freq=2472 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=14 freq=2484 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=34 freq=5170 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=38 freq=5190 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=42 freq=5210 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=46 freq=5230 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=144 freq=5720 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=149 freq=5745 MHz max_tx_power=13 dBm
Allowed channel: mode=2 chan=153 freq=5765 MHz max_tx_power=13 dBm
Allowed channel: mode=2 chan=157 freq=5785 MHz max_tx_power=13 dBm
Allowed channel: mode=2 chan=161 freq=5805 MHz max_tx_power=13 dBm
Allowed channel: mode=2 chan=165 freq=5825 MHz max_tx_power=13 dBm
Allowed channel: mode=2 chan=169 freq=5845 MHz max_tx_power=13 dBm
Allowed channel: mode=2 chan=0 freq=5920 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=23441 freq=5940 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=0 freq=5960 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=23361 freq=5980 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=0 freq=6000 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=23281 freq=6020 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=0 freq=6040 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=23201 freq=6060 MHz max_tx_power=0 dBm
Allowed channel: mode=2 chan=0 freq=6080 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=12 freq=2467 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=13 freq=2472 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=14 freq=2484 MHz max_tx_power=20 dBm
hw vht capab: 0x10b0, conf vht capab: 0x0
DFS support is enabled
Completing interface initialization
Mode: IEEE 802.11a Channel: 36 Frequency: 5180 MHz
DFS 0 channels required radar detection
Could not set channel for kernel driver
Interface initialization failed
wlan0: interface state COUNTRY_UPDATE->DISABLED
wlan0: AP-DISABLED
wlan0: Unable to setup interface.
hostapd_interface_deinit_free(0x55791746a950)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x55791746a950)
wlan0: interface state DISABLED->DISABLED
hostapd_bss_deinit: deinit bss wlan0
wlan0: Deauthenticate all stations
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> -22 (Invalid argument)
wlan0: AP-DISABLED
hostapd_cleanup(hapd=0x55791746bc50 (wlan0))
wlan0: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wlan0 wasn't started
hostapd_interface_deinit_free: driver=0x557915b9c960 drv_priv=0x55791746c7d0 -> hapd_deinit
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
nl80211: Disable Probe Request reporting nl_preq=0x8888ddf19fce41e9
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=15)
netlink: Operstate: ifindex=15 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 15 iftype 2 (STATION)
nl80211: Teardown AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Unsubscribe mgmt frames handle 0x8888ddf19fce3a59 (AP teardown (dev SME))
hostapd_interface_free(0x55791746a950)
hostapd_interface_free: free hapd 0x55791746bc50
hostapd_cleanup_iface(0x55791746a950)
hostapd_cleanup_iface_partial(0x55791746a950)
hostapd_cleanup_iface: free iface=0x55791746a950

hostapd.conf
interface=wlan0
bridge=br0
driver=nl80211
ssid=SOMETHING
country_code=DE
ieee80211d=1
ieee80211h=1
hw_mode=a
channel=36
wmm_enabled=1
ieee80211n=1
require_ht=1
ieee80211ac=1
require_vht=1
vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=42
wpa=2
wpa_passphrase=something
wpa_key_mgmt=WPA-PSK
rsn_pairwise=CCMP

Uncommenting ieee80211ac=1 results in the access point being created just fine, albeit in 802.11n mode only.

I am using TP-Link Archer T4UHP which is rtl8812au chip. I installed the latest (v5.1.5, commit aa590f3) driver.

When doing deauthentication to 2.4GHz target, the speed is very slow and just a few or no acknowlege from AP or client most of time even I am very close to the AP and client. However, it captures the handshake finally.

Furthermore, when doing deauthentication to 5GHz target, the speed is very very slow and there is no acknowlege from AP and client. Handshake cannot be captured.

By the way, I am using USB 2.0 on my laptop and Kali Linux 2017.3 with the latest updates.