Open haraldrudell opened 4 years ago
macOS client bcm43602 reports channel 878 Mb/s mcs 7: 3x3 80 MHz iperf3 throughput 451 Mb/s 😄😄😄 and AP does not crash…
echo "options 88XXau rtw_switch_usb_mode=1 rtw_led_ctrl=0" >/etc/modprobe.d/8812au.conf … cat /proc/net/rtl88XXau/wlx08beac12be7a/led_ctrl 0 cat /sys/module/88XXau/parameters/rtw_switch_usb_mode 1 no change
the STA works with 802.11g 54 Mb/s: iperf3 18.5 Mb/s
Just a workaround patch for that case, but yet 8814 has a performance issue though.
This driver, which claims to be 5.8.5 does work at 469 Mb/s: https://github.com/coolshou/rtl8814au
Basically:
# rmmod and make uninstall or ./dkms-remove.sh of whatever was there before cd ~ git clone --depth 1 https://github.com/coolshou/rtl8814au.git coolshou cd coolshou/driver nano ./os_dep/linux/usb_intf.c # 191 is: {USB_DEVICE(0x2001, 0x331a), .driver_info = RTL8814A}, /* D-Link - D-Link */ # add after line 191: {USB_DEVICE(0x7392, 0xA833), .driver_info = RTL8814A}, /* Edimax - AC1750 */ # echo "options 8814au rtw_switch_usb_mode=1" >/etc/modprobe.d/8814au.conf make make install modprobe 8814au cat /sys/module/8814au/version 5.8.5-34085 cat /sys/module/8814au/parameters/rtw_switch_usb_mode 1 # check what devices driver claims: modprobe -c | egrep '8814au$' alias usb:v0BDAp8813d*dc*dsc*dp*ic*isc*ip*in* 8814au alias usb:v2001p331Ad*dc*dsc*dp*ic*isc*ip*in* 8814au alias usb:v7392pA833d*dc*dsc*dp*ic*isc*ip*in* 8814au # plug in Wi-Fi device lsusb -t | grep 8814au |__ Port 3: Dev 6, If 0, Class=Vendor Specific Class, Driver=rtl8814au, 5000M ip l | grep wlx 8: wlx08beac12be7a:mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 iw dev phy#4 Interface wlx08beac12be7a ifindex 7 wdev 0x400000001 addr 08:be:ac:12:be:7a type managed txpower 20.00 dBm phy#0 Interface wlp3s0 ifindex 4 wdev 0x1 addr f4:5c:89:8a:29:2f type managed channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz # device is phy4 rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 blocked unblocked 2 wlan phy0 blocked unblocked 5 wlan phy4 blocked unblocked # id is 5 rfkill unblock 5 # # configure interface ip l sh wlx08beac12be7a # should be state UP mode DEFAULT ip l s wlx08beac12be7a up iw wlx08beac12be7a connect entebbe iw wlx08beac12be7a link Connected to 08:be:ac:12:be:74 (on wlx08beac12be7a) SSID: entebbe freq: 5180 signal: -48 dBm tx bitrate: 1300.0 MBit/s # 1300 is what we want to see ip a s wlx08beac12be7a dhclient wlx08beac12be7a iperf3 --client 10.36.0.1 472 Mbits/sec 0 sender 469 Mbits/sec receiver 😄😄😄
aircrack-ng is broken somehow but did take code from this repo
Now, gentlemen, you have a working and a failing case, and we know it can be done!
Just a workaround patch for that case, but yet 8814 has a performance issue though.
Applying that patch removes the crash but does not increase throughput. Bug still there
@haraldrudell Yeah, finally a more clean driver for that chipset also, rtl8812au and rtl8821au is quite similar, rtl8814au code never was..
@fariouche Here's some news for us 🥇
The import commit is found below, seems legit, checked history for rtw_version.h tampering, but it seems it's a vendor release, not pure Realtek but it looks good!
)
Ok, this is a driver developed by Edimax actually. Vedpr based.
Here's the link to ZIP below; https://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-7833UAC/EW-7833UAC_linux_5.8.5.1_kernel_2.6-5.1.zip
What I'll do, I'll compare it to the past release of 8814au and see what changed. Damn!
Realtek rtl8814au from 2010 is Wi-Fi 5 802.11ac 4x4:3 AC1900: 1.3 Gb/s on 5 GHz 80 MHz and 600 Mb/s on 2.4 GHz 40 MHz
That makes it the fastest usb chip at present until 4x4:4 or Wi-Fi 6 802.11ax is available. And it is supported or at least working on Linux/macOS/Windows. The maximum speed calls for a usb3 port at 5 Gb/s or better
At least for Linux, Access Point and Wi-Fi Direct is supported, too. That means we have a dual band eap-tls or wpa3 with continuous security updates
NETGEAR A7000 seems to have put the best antennas on it but there are many like: D-Link DWA-192, Edimax EW7833UAC, TP-Link Archer T9UH
Tube-UAC2 with directional panel.. beats everything. Like a magic wand 👍
Some additional differences:
Neither driver supports multiple ssids: iw list interface combinations are not supported
The coolshou driver does not have the radar detection channels 52…144 but has channels 144…177 disabled, 14 disabled
coolshou driver does not have: HT 2.4/5 GHz: RX Greenfield RX STBC 3-streams VHT 5 GHz: > [RX-STBC-1] ie. the coolshou driver does not: — offer non-backwards compatible, higher performing HT channel: 2.4 GHz 802.11n performance — receive multiple spatial streams
coolshou does not have command: set_wiphy_netns
The conclusion is, as of October 17th, 2020: use 88XXau for AP use 8814au for STA
I am not sure if those software capability descriptions is what the hardware is actually doing
The coolshou driver could receive at 469 Mb/s on 5 GHz as verified by iperf3. That speed will only be attained when using all 3 spatial streams
It seems that SAE WPA3-Personal does not work as STA or AP 8814 does not have protected management frames, but does have SAE iw list … MFP-capable # is missing Device supports SAE with AUTHENTICATE command
Because the driver has no combinations, multi-band AP or multi-ssid authentication like guest network is unavailable
For reference, here is iw list output for the 88XXau aircrack-ng driver and rtl8814au. This data can be difficult to come by
— multiple ssids is not supported “interface combinations are not supported” so multi-band AP or guest network involves adding more adapters — protected management frames is not supported 802.11w, so it will not work with certified WPA3 hardware that will reject this device: iw list “MFP-capable” — SAE, ie. WPA3 authentication, is supported “Device supports SAE with AUTHENTICATE command” — — SAE is as of now the only safe password-based Wi-Fi of any kind — — SAE makes password attacks unfeasible for passwords that are difficult to guess — — SAE mutually authenticates STA and AP like eap-tls, they must both prove to have the secret — — Wi-Fi security that is not eap-tls prior to 2018 is garbage as is much embedded software out of China
There are no mfp usb adapters for Linux as of yet Recent built-in pci chipsets offer mfp, for example the Raspberry Pi 4’s Broadcom
The best use of this AC1900 hardware is 469 Mb/s browsing throughput on 1.3 Gb/s 5 GHz 80 MHz eap-tls. We’ll all enjoy very safe amazing performance. No known vulnerabilities whatsoever since 0 BC
Wiphy phy3 max # scan SSIDs: 9 max scan IEs length: 2304 bytes max # sched scan SSIDs: 0 max # match sets: 0 max # scan plans: 1 max scan plan interval: -1 max scan plan iterations: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) * CMAC (00-0f-ac:6) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed * AP * monitor Band 1: Capabilities: 0x1963 RX LDPC HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI RX STBC 1-stream Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 16 usec (0x07) HT Max RX data rate: 450 Mbps HT TX/RX MCS rate indexes supported: 0-23 Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps * 5.5 Mbps * 11.0 Mbps * 6.0 Mbps * 9.0 Mbps [90/1951] * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) * 2472 MHz [13] (20.0 dBm) * 2484 MHz [14] (disabled) Band 2: Capabilities: 0x1863 RX LDPC HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI No RX STBC Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 16 usec (0x07) HT Max RX data rate: 450 Mbps HT TX/RX MCS rate indexes supported: 0-23 VHT Capabilities (0x03c051b2): Max MPDU length: 11454 Supported Channel Width: neither 160 nor 80+80 RX LDPC short GI (80 MHz) TX STBC SU Beamformee +HTC-VHT VHT RX MCS set: 1 streams: MCS 0-9 2 streams: MCS 0-9 3 streams: MCS 0-9 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT RX highest supported: 1300 Mbps VHT TX MCS set: 1 streams: MCS 0-9 [35/1951] 2 streams: MCS 0-9 3 streams: MCS 0-9 4 streams: not supported 5 streams: not supported 6 streams: not supported 7 streams: not supported 8 streams: not supported VHT TX highest supported: 1300 Mbps Bitrates (non-HT): * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Frequencies: * 5180 MHz [36] (23.0 dBm) * 5200 MHz [40] (23.0 dBm) * 5220 MHz [44] (23.0 dBm) * 5240 MHz [48] (23.0 dBm) * 5260 MHz [52] (23.0 dBm) * 5280 MHz [56] (23.0 dBm) * 5300 MHz [60] (23.0 dBm) * 5320 MHz [64] (23.0 dBm) * 5500 MHz [100] (23.0 dBm) * 5520 MHz [104] (23.0 dBm) * 5540 MHz [108] (23.0 dBm) * 5560 MHz [112] (23.0 dBm) * 5580 MHz [116] (23.0 dBm) * 5600 MHz [120] (23.0 dBm) * 5620 MHz [124] (23.0 dBm) * 5640 MHz [128] (23.0 dBm) * 5660 MHz [132] (23.0 dBm) * 5680 MHz [136] (23.0 dBm) * 5700 MHz [140] (23.0 dBm) * 5720 MHz [144] (disabled) * 5745 MHz [149] (30.0 dBm) * 5765 MHz [153] (30.0 dBm) * 5785 MHz [157] (30.0 dBm) * 5805 MHz [161] (30.0 dBm) * 5825 MHz [165] (30.0 dBm) * 5845 MHz [169] (disabled) * 5865 MHz [173] (disabled) * 5885 MHz [177] (disabled) Supported commands: * new_interface * set_interface * new_key * start_ap * new_station * set_bss * join_ibss * set_pmksa * del_pmksa * flush_pmksa * remain_on_channel * frame * set_channel * connect * disconnect Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0xd0 * managed: 0x40 0xb0 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 WoWLAN support: * wake up on anything (device continues operating normally) software interface modes (can always be added): * monitor interface combinations are not supported Device supports SAE with AUTHENTICATE command Device supports scan flush. Supported extended features:
Works as AP but not as STA STA connecting to slow 54 Mb/s 802.11g AP works Crash: STA connecting to 3x3:3 1.3 Gb/s AC1900 rtl8814
Have an access point 5 GHz 80 MHz 3x3:3 running
iperf3 --server
https://github.com/haraldrudell/AC1300-USB/blob/master/README.mdHave a usb3 computer with device up in 5 Gb/s mode:
less /var/log/syslog