Access Point Mode about rtl8812au HOT 59 OPEN

FWIW I was able to get the AP working on the 5 GHz band with 135 Mbps albeit only in 802.11n/ht 40MHz. I was not able to get the 802.11ac/vht features working. iperf measures ~8.00 MBytes/sec 67.1 Mbits/sec. Not optimal, but works for me.
Driver used: https://github.com/abperiasamy/rtl8812AU_8821AU_linux
hostap config + details are here: https://gist.github.com/evilJazz/db1b2f4254f678406dd3

from rtl8812au.

I did. My phone (Samsung S7) connects at 866 Mbit/s ... to 8812AU based AP. It works on all Armbian builds out of the box with a kernel 4.9 or higher. The driver (not exactly this one but a modified version of this) is built into several kernels. Check how to video. At that time of recording it was not resolved but now it's working in AC mode, dual stream, probably more with 8814 but I don't have a proper client to verify.

from rtl8812au.

AdHoc isn't the same as making an AP. For creating an AP you would use Hostapd

from rtl8812au.

Yes, it's default one and configuration as well. This chipset is one of many that is laying around and I hope to get out of it more than from others - in AP mode.

https://github.com/igorpecovnik/lib/blob/next/config/hostapd.conf

from rtl8812au.

@JohnMHarrisJr are you for real? Neither of those has 11ac support. OF COURSE there are tons of options for Linux without 11ac. But rather than mindlessly copypasting ThinkPenguin SKUs (which are just overpriced versions of the 100% same devices you can get from China directly btw), why not think about the reasons we want to use this particular device first.

And I dunno what $100 you refer to (a post from 2014?), 8812au-based devices cost $10-15 by now. While yours are priced at $59 and $81.

from rtl8812au.

I'never tried setting up an access point with the dongle, but I guess you do it the same way you do for every WIFI adapter, i.e. like this.

from rtl8812au.

Thank you! I really appreciate your advice!

from rtl8812au.

Can someone confirm that it can be set to master mode with hostapd on the 5GHz band? I don't want to spend $100 on a card unless it can.

from rtl8812au.

I insert a diff against Fedora hostapd.conf for someone to try:

--- hostapd.conf.orig   2013-05-30 21:28:17.000000000 +0300
+++ hostapd.conf        2013-06-04 23:36:48.253877933 +0300
@@ -22,19 +22,19 @@
 ignore_broadcast_ssid=0

 # Uncomment these for base WPA & WPA2 support with a pre-shared key
-#wpa=3
-#wpa_key_mgmt=WPA-PSK
-#wpa_pairwise=TKIP
-#rsn_pairwise=CCMP
+wpa=2
+wpa_key_mgmt=WPA-PSK
+wpa_pairwise=TKIP
+rsn_pairwise=CCMP

 # DO NOT FORGET TO SET A WPA PASSPHRASE!!
-#wpa_passphrase=YourPassPhrase
+wpa_passphrase=Your_passkey

 # Most modern wireless drivers in the kernel need driver=nl80211
 driver=nl80211

 # Customize these for your local configuration...
-interface=
-hw_mode=
-channel=
-ssid=
+interface=wlan0
+hw_mode=a
+channel=36
+ssid=Your_AP_name

You can try other settings from http://wireless.kernel.org/en/users/Drivers/ath10k/configuration#Configuring_hostapd

from rtl8812au.

It does work as an access point (on the RaspberryPI) at 5GHz but requires some of the above tweaks, and I use a patched hostapd that supports some more rtl drivers - http://www.daveconroy.com/turn-your-raspberry-pi-into-a-wifi-hotspot-with-edimax-nano-usb-ew-7811un-rtl8188cus-chipset/ which is prepatched from https://github.com/pritambaral/hostapd-rtl871xdrv. (I'm now using an odroidw which is a limited edition clone with battery, rtc, etc.). It isn't always stable, but it might be part of my configuration or startup ordering (with the ethernet, my jetpack, bluetooth bnep...), and with wpa_supplicant to do PEAP

from rtl8812au.

Thank you tz1. I can get it to run with those patches and the previous version of hostapd (2.2). But not with the driver from this repo. Instead I'm using rtl8812AU_8821AU_linux from abperiasamy here on github. It works with 80211n in 5Ghz but not 80211ac, it could be my fault though, I'm merely uncommenting the line ieee80211ac=1. I don't know if I need to do change/add anything else in my hostapd.conf to get it ac mode to work.

RTM_NEWLINK: ifi_index=5 ifname=wlp7s0u1 wext ifi_flags=0x1003 ([UP])
nl80211: Event message available
nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlp7s0u1
wlp7s0u1: nl80211: New scan results available
nl80211: Scan included frequencies: 5180 5190 5200 5210
wlp7s0u1: Event SCAN_RESULTS (3) received
nl80211: Received scan results (7 BSSes)
HT40: control channel: 36  secondary channel: 40
Completing interface initialization
Mode: IEEE 802.11a  Channel: 36  Frequency: 5180 MHz
DFS 0 channels required radar detection
nl80211: Set freq 5180 (ht_enabled=1, vht_enabled=1, bandwidth=80 MHz, cf1=5210 MHz, cf2=0 MHz)
nl80211: Failed to set channel (freq=5180): -22 (Invalid argument)
Could not set channel for kernel driver
Interface initialization failed
wlp7s0u1: interface state HT_SCAN->DISABLED
wlp7s0u1: AP-DISABLED 
hostapd_interface_deinit_free(0x931860)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x931860)
hostapd_bss_deinit: deinit bss wlp7s0u1
wlp7s0u1: Deauthenticate all stations
nl80211: sta_remove -> DEL_STATION wlp7s0u1 ff:ff:ff:ff:ff:ff --> -22 (Invalid argument)
hostapd_cleanup(hapd=0x933b40 (wlp7s0u1))
hostapd_free_hapd_data: Interface wlp7s0u1 wasn't started
hostapd_interface_deinit_free: driver=0x4a3740 drv_priv=0x9348e0 -> hapd_deinit
nl80211: Skip disabling of Probe Request reporting nl_preq=0x88888888881ba959 while in AP mode
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=5)
netlink: Operstate: ifindex=5 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 5 iftype 2 (STATION)
nl80211: Teardown AP(wlp7s0u1) - device_ap_sme=1 use_monitor=1
nl80211: Disable Probe Request reporting nl_preq=0x88888888881ba959
hostapd_interface_free(0x931860)
hostapd_interface_free: free hapd 0x933b40
hostapd_cleanup_iface(0x931860)
hostapd_cleanup_iface_partial(0x931860)
hostapd_cleanup_iface: free iface=0x931860

from rtl8812au.

Hey Thor could you post your config?

from rtl8812au.

Hi Hans, this one "works" for me, although not as good I i wished for.

interface=wlp6s0u1
ssid=myssid
country_code=SE
ieee80211d=1
hw_mode=a
channel=40
macaddr_acl=0
auth_algs=3
wmm_enabled=1
ieee80211ac=1
vht_capab=[SHORT-GI-80][SHORT-GI-160][VHT160-80PLUS80][MU-BEAMFORMER][MU-BEAMFORMEE][SU-BEAMFORMER][SU-BEAMFORMEE]
require_vht=0
#vht_oper_chwidth=1                                                                                                                                           
vht_oper_centr_freq_seg0_idx=40
#vht_oper_centr_freq_seg1_idx=44

So I got 5GHz AC to work if I turn N off completely. But I'm stuck at 54Mbps (~26Mbps real world) and it wont go faster than that. whatever I try to configure vht_oper_chwidth to makes hostapd exit.

I have tried a lot of different combinations in vht_capab but they don't seem to have much effect on the bitrate, except if I leave it empty the speed will get even worse.

from rtl8812au.

Try with my hostapd v2.4 ... AC is enabled and also wide channel override hack:
https://github.com/igorpecovnik/lib/blob/next/bin/hostapd24.tgz

from rtl8812au.

igorpecovnik: That's an ARM 32bit binary. Would you mind providing the source? Or at least provide a x86_64 binary? It would be much appreciated.

from rtl8812au.

Oh, ARM yes. I am too much in this :) The exact source is gone but as I remember I fork latest development hostapd, applied this patch:
http://patchwork.ozlabs.org/patch/144477/ (maybe not exactly this but it covers the same problem) and alter configuration before compilation to enable AC and maybe something else. I am also going to test how much I can get out of it.

from rtl8812au.

Wow thanks Igor, is this the default hostapd that comes with your latest image? Also thanks for the instructions for compiling this driver.

Could you post your hostapd.conf file that you use?

from rtl8812au.

noob question:
my phones can see the ap but both of them does not connect. luckily my nexus 5 actually says obtaining IP adress and give up after a few seconds. my zenfone 2 doesnt show anything but connecting.
im guessing that my computer does not assign an ip address.
so how can i convince my linuxmint to give some ip address to my phones. also how do i share the internet to them?
i mean i need a good tutorial....after all i'm a noob to this kind of things.
im still trying to make the adapter....a few more days and ill give up trying and send it back.

Edit: I've manage to connect/get access to internet. now the problem is that download speed is limited to around 30Mbps no matter the connection speed. upload seems to do just fine (around 60-70mbps)

from rtl8812au.

Thanks so much for this repository. I have an Edimax EW-7811UAC and this driver and hostapd 2.5 compiled for the original Raspberry PI work quite well.

I do have the same issue that I am unable to take advantage of any of the AC capabilities. Any time I set vht_oper_chwidth to a value other than 0 (I've been trying 1 for 80mhz channel width), hostapd will error out and say it could not set the channel.

I did modify hostapd as suggested at the link http://home.icequake.net/~nemesis/blog/index.php/archives/619/comment-page-1 so that it would allow setting vht_capab without erroring as well. Even with vht_capab commented out, I cannot set the channel width to anything above 40mhz and I cannot get more than ~135mbs from my devices that support AC.

Has anyone gotten full AC bandwidth to work?

from rtl8812au.

+1

from rtl8812au.

I inhibited vht_capab error like zaphod24's link says.
I applied a following patch to skip forneighboring BSS checking.
http://patchwork.ozlabs.org/patch/144477/
And finally I got 300Mbps on 802.11n capable laptop.
Right now, I don't have 802.11ac capable machines, so I can't test it unfortunately.

from rtl8812au.

Tried the patch referenced above to skip neighboring BSS checks.

When I try to enabled VHT with:

vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=155

I get the error:

nl80211: Failed to set channel (freq=5785): -22 (Invalid argument)
Could not set channel for kernel driver

from rtl8812au.

I confirmed that it does not work as 802.11ac AP.
I doubt rtl8812au driver is capable of VHT. I don't think patching hostapd will help.
I did a lot of googling about, but nobody seems to be able to go beyond 300Mbps (802.11n).

from rtl8812au.

I get 867mbs routinely on several different manufacturers' implementations running as a straight up wifi adapter connected to commercial ac1200 and ac3200 commercial routers. If your comment is hostapd specific; never mind, no knowledge of it.

from rtl8812au.

It's hostapd related, but it is caused either by 8812au chipset or the driver, because hostapd supports 802.11ac.
I'm starting to think that rtl8812au chipset doesn't simply support AP mode in 802.11ac.
.

from rtl8812au.

@smekkley @zaphod24 @evilJazz
Actually it is not hostapd related but driver related. It seems that Realtek did not include the vital functions which state the card's VHT capability. Hostapd wrongly believes that the card does not support 802.11ac so it refuse to start an AP.
The modified driver is available at https://github.com/uminokoe/rtl8812AU.
Note: Using RTL8811AU, the iperf3 result is around 220 Mbps. RTL8812AU's speed has not yet been tested.

In addition, Realtek built regulatory compliance into the driver (os_dep/linux/wifi_regd.c), which is too restrictive and disables many channels. This means that you may encounter problems when they try to set up an AP in 802.11ac mode. To remove the restriction, change CONFIG_DISABLE_REGD_C = n to CONFIG_DISABLE_REGD_C = y in Makefile.

from rtl8812au.

@uminokoe
Wow, you are like a programming prodigy for me.
It looks like it is working with my AUKEY WF-R6.

I don't have 802.11ac compatible client right now, so I cannot confirm.
Did you benchmark with iperf3? Mine goes no more than 250Mbps with 802.11n.

from rtl8812au.

If your chipset is RTL8812AU, it should support 2T2R. Neither 80+80MHz nor 160MHz is supported for that chipset.

Card 1: 1T1R / 160MHz
Card 2: 2T2R /  80MHz
Result: 1T1R /  80MHz (PHY link rate: 433 Mbps)
---------------------
Card 3: 1T1R / 160MHz
Card 4: 1T1R / 160MHz
Result: 1T1R / 160MHz (PHY link rate: 867 Mbps)
---------------------
Card 5: 2T2R /  80MHz
Card 6: 2T2R /  80MHz
Result: 2T2R /  80MHz (PHY link rate: 867 Mbps)

from rtl8812au.

@uminokoe

Mine is RTL8812AU. I'll try that as soon as I get proper 802.11ac compatible machine. Thank you!

You should try with UDP when you use iperf3 because TCP overhead is a lot greater than UDP generally speaking.
Example command is like below.
iperf3 -c 'IP address of the server' -u -b 433M
But I guess if it's android it is unlikely that it goes over 433M, because when I tested with 802.11n,
Arch Linux I could only go up to 190Mbps, while Windows on the same machine could go up to 250Mbps.

from rtl8812au.

So I've tested using iperf3 on an iPhone 6 Plus (the only device I have that is AC) with an older N-only 5ghz router (Cisco E2000) running dd-wrt and also at work with Cisco access points and I get ~100mbit in both cases.

After the updated driver and specifying vht_oper_chwidth=1 (should be 80mhz) I can get ~220mbit against my Edimax EW-7811UAC. That's definitely better than before (max ~130mbit) although not anywhere near the theoretical max.

Unfortunately none of my other devices even claim to be AC, so I can't see if there is some limitation in the iPhone.

from rtl8812au.

@zaphod24
You may want to know what speed others get. According to this blog What's New (and Missing) in the WiFi for iPhone 6,

The iPhone 6 and iPhone 6 Plus are non-MIMO 802.11ac devices. That means a top rate of 433 Mbps.

And according to this reddit What is the max wifi Speed of an IPhone 6?, the Speedtest.net by Ookla results of iPhone 6 (which the Wi-Fi max speed is the same as iPhone 6 Plus) are 279_{Mbps Download} and 212_{Mbps Upload}.
I really hope that one day this driver can appear in upstream Linux kernel. By then, I guess people will aware of this chipset and may make contributions to it. It seems that in terms of USB adapters, RTL8812AU series is one of the few choices which support 802.11ac AP mode and have probable (and open source) Linux driver.

from rtl8812au.

Yep, I would definitely be interested in what success and speed others have. I've got my EW-7811UAC plugged into a Raspberry PI 2, so really the best I can get onto the LAN is 100mbit anyway, but from a wireless device to the PI I should be able to get up to 433mbit using iperf3. Some of that depends on what else is on the shared USB bus that tops out at 480mbit.

I'm actually running 2 of the EW-7811UAC, one in 2.4ghz N mode and the other in 5ghz AC mode. They're pretty decent devices for $25 and combined with an RPi2 that I had laying around they make for a decent access point and some experimentation.

I appreciate the speed boost to 200+mbit compared to the unmodified 8812au driver.

from rtl8812au.

I finally got my hands around to 802.11ac compatible laptop.
I get 273 Mbits/sec with iperf3, but Windows wireless property reports that the signal is 866.7 Mbps.
With TCP, I get 160Mbps so it's faster than my LAN.
Strangely enough, it also reports that the access point is 802.11n.
I guess it is a limit of my wireless card or its builtin driver on my laptop.
The dongle is attached to USB2.0 on raspberry pi, so it should be able to perform up to about 480Mbps.

from rtl8812au.

Wikidevi says that my chipset(Intel Dual Band Wireless-AC 7265) supports 2T2R and 2 spatial streams.
I am using Windows 7.

--iw list--

Wiphy phy0
        max # scan SSIDs: 9
        max scan IEs length: 2304 bytes
        max # sched scan SSIDs: 0
        max # match sets: 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 (00-0f-ac:4)
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * monitor
                 * P2P-client
                 * P2P-GO
        Band 1:
                Capabilities: 0x1972
                        HT20/HT40
                        Static SM Power Save
                        RX Greenfield
                        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: 300 Mbps
                HT TX/RX MCS rate indexes supported: 0-15
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps
                        * 5.5 Mbps
                        * 11.0 Mbps
                        * 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:
                        * 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) (no IR)
                        * 2472 MHz [13] (20.0 dBm) (no IR)
                        * 2484 MHz [14] (disabled)
        Band 2:
                Capabilities: 0x1872
                        HT20/HT40
                        Static SM Power Save
                        RX Greenfield
                        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: 300 Mbps
                HT TX/RX MCS rate indexes supported: 0-15
                VHT Capabilities (0x038002a0):
                        Max MPDU length: 3895
                        Supported Channel Width: neither 160 nor 80+80
                        short GI (80 MHz)
                        TX STBC
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: not supported
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT RX highest supported: 0 Mbps
                VHT TX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: not supported
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT TX highest supported: 0 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:
                        * 5170 MHz [34] (disabled)
                        * 5180 MHz [36] (30.0 dBm)
                        * 5190 MHz [38] (disabled)
                        * 5200 MHz [40] (30.0 dBm)
                        * 5210 MHz [42] (disabled)
                        * 5220 MHz [44] (30.0 dBm)
                        * 5230 MHz [46] (disabled)
                        * 5240 MHz [48] (30.0 dBm)
                        * 5260 MHz [52] (20.0 dBm) (no IR)
                        * 5280 MHz [56] (20.0 dBm) (no IR)
                        * 5300 MHz [60] (20.0 dBm) (no IR)
                        * 5320 MHz [64] (20.0 dBm) (no IR)
                        * 5500 MHz [100] (23.0 dBm) (no IR)
                        * 5520 MHz [104] (23.0 dBm) (no IR)
                        * 5540 MHz [108] (23.0 dBm) (no IR)
                        * 5560 MHz [112] (23.0 dBm) (no IR)
                        * 5580 MHz [116] (23.0 dBm) (no IR)
                        * 5600 MHz [120] (23.0 dBm) (no IR)
                        * 5620 MHz [124] (23.0 dBm) (no IR)
                        * 5640 MHz [128] (23.0 dBm) (no IR)
                        * 5660 MHz [132] (23.0 dBm) (no IR)
                        * 5680 MHz [136] (23.0 dBm) (no IR)
                        * 5700 MHz [140] (23.0 dBm) (no IR)
                        * 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)
                        * 5920 MHz [184] (disabled)
                        * 5940 MHz [188] (disabled)
                        * 5960 MHz [192] (disabled)
                        * 5980 MHz [196] (disabled)
                        * 6000 MHz [200] (disabled)
                        * 6020 MHz [204] (disabled)
                        * 6040 MHz [208] (disabled)
                        * 6060 MHz [212] (disabled)
                        * 6080 MHz [216] (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 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 scan flush.

--iwconfig--

wlan0     IEEE 802.11AC  ESSID:"My SSID"  Nickname:"<WIFI@REALTEK>"
          Mode:Master  Frequency:5.18 GHz  Access Point: "My MAC Address"  
          Bit Rate:867 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=70/100  Signal level=100/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

from rtl8812au.

If you are testing the TCP throughput with iperf3, please try increasing the window size to 100M. In addition, the test should be long enough, such as 15 seconds. In the first few seconds of the test, the speed has not yet reach the maximum.

from rtl8812au.

I tried with 20M windows with 15 seconds, but it did not go more than UDP. It was just about 200Mbps.
I also booted the laptop with arch linux usb media and measured, but it was worse than windows 7.
I forced the hostapd to drop access other than 802.11ac by setting "require_vht=1", but it did not change.
From a laptop incompatible with 802.11ac, I could not connect to the access point, so the configuration should be right. It feels like that it is either the raspberry pi's limitation or the driver.

from rtl8812au.

@smekkley
hi, which driver do you use for rtl8812au devices? If it's from uminokoe, do you have a copy, seems he delete his account.

from rtl8812au.

@thorwald Instead of "spend[ing] $100 on a card", why not get a different device which has better Linux support?

Depending on your device, I would suggest https://www.thinkpenguin.com/gnu-linux/wireless-n-dual-band-bluetooth-40-m2-ngff-combo-card or https://www.thinkpenguin.com/gnu-linux/wireless-n-pci-express-dual-band-mini-half-height-card-tpe-nhmpcied2

from rtl8812au.

Any one achieved AC mode with 433Mbps in Access Point ?

from rtl8812au.

So, do i need to update driver after installing Armbian ( for raspberry Pi) ? Or it will work out of box ?

from rtl8812au.

There are few problems with this plan. There is no support for RaspberryPi within Armbian which means this will not work out of the box. It will be a little longer path ... software wise you need to build a module. It should work if you use some decent OS. Hardware - one AC stream is maximum for power supply and USB bandwidth reasons. Get some board with better I/O performance first. Almost any is better for this job.

from rtl8812au.

Surprised Armbian doesn't support PI !!!!
Any way i have Pi 2 which is better in performance and have Diet pi as OS. Can you point me which driver has all fixes and hostapd conf to use to make it work. I will compile and load driver, with given hostapd config.

from rtl8812au.

Armbian is not a commercial project so why bother with supporting a closed hardware toy? :) Read this to understand broader motives.

Anyway I have Pi 2 which is better in performance and have Diet pi as OS.

RPi 1,2 and 3 have the same design issues which are essential in this case. Everything is connected via one USB port and bandwidth has to be shared which simply means Rpi is performing terribly at any I/O operation ...

Those 8811/8812 & 8814AU chips usually come with USB3 (but can work on 2.0 if powering is done properly) can easily draw 600-700mA and Rpi is not able to secure even 500mA.

It should work if you use some decent OS

Dietpi is a stripped, crippled and rebranded Raspbian with a lot of bloatware where advanced features come last. If.

Check reasons why this job is simple on Armbian.

Is some crippled AP still possible? You need to establish build environment, adjust patches, recompile kernel, hostapd but before even starting you need to install a lot of essentials which were removed by Dietpi in the name of marketing, stupidity or ignorance? Then you need to add external self-powered USB hub and you will never achieve speeds that are possible on any cheap Chinese board.

I would suggest you to rather invest 15-20USD for a decent & capable hardware.

from rtl8812au.

I complied driver from https://github.com/abperiasamy/rtl8812AU_8821AU_linux. Kind of working, i can see SSID but can't. Looks like more debug to do. Any link for changes to be would be help full.

from rtl8812au.

I see SSID in PC but not able to connect. here is Hostapd log. Pls check what is the issue.

root@DietPi:~# sudo hostapd -dd /etc/hostapd/hostapd.conf
random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd.conf
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=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: Using driver-based off-channel TX
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 phy0
nl80211: Set mode ifindex 3 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=1
nl80211: Enable Probe Request reporting nl_preq=0xb5c038
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0xb5c038 match=
nl80211: QCA vendor test command returned -95 (Operation not supported)
nl80211: Add own interface ifindex 3
nl80211: if_indices[16]: 3
nl80211: Add own interface ifindex 12
nl80211: if_indices[16]: 3 12
nl80211: Adding interface wlan0 into bridge br0
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code IN, new country code IN
nl80211: Regulatory information - country=IN (DFS-JP)
nl80211: 2402-2482 @ 40 MHz 20 mBm
nl80211: 5170-5250 @ 80 MHz 20 mBm
nl80211: 5250-5330 @ 80 MHz 20 mBm (DFS)
nl80211: 5735-5835 @ 80 MHz 20 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=13 freq=2472 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=40 freq=5200 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=48 freq=5240 MHz max_tx_power=20 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=13 freq=2472 MHz max_tx_power=20 dBm
Completing interface initialization
Mode: IEEE 802.11a Channel: 40 Frequency: 5200 MHz
DFS 0 channels required radar detection
nl80211: Set freq 5200 (ht_enabled=0, vht_enabled=1, bandwidth=20 MHz, cf1=5200 MHz, cf2=0 MHz)

• freq=5200
• vht_enabled=1
• ht_enabled=0
• bandwidth=20
• channel_width=1
• center_freq1=5200
• center_freq2=0
  RATE[0] rate=60 flags=0x1
  RATE[1] rate=90 flags=0x0
  RATE[2] rate=120 flags=0x1
  RATE[3] rate=180 flags=0x0
  RATE[4] rate=240 flags=0x1
  RATE[5] rate=360 flags=0x0
  RATE[6] rate=480 flags=0x0
  RATE[7] rate=540 flags=0x0
  hostapd_setup_bss(hapd=0xb5b9a0 (wlan0), first=1)
  wlan0: Flushing old station entries
  nl80211: flush -> DEL_STATION wlan0 (all)
  wlan0: Deauthenticate all stations
  nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> -22 (Invalid argument)
  wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
  wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
  wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
  wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
  Using interface wlan0 with hwaddr 78:32:1b:0a:0f:37 and ssid "test1"
  Deriving WPA PSK based on passphrase
  SSID - hexdump_ascii(len=5):
  74 65 73 74 31 test1
  PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
  PSK (from passphrase) - hexdump(len=32): [REMOVED]
  random: Got 20/20 bytes from /dev/random
  Get randomness: len=32 entropy=0
  GMK - hexdump(len=32): [REMOVED]
  Get randomness: len=32 entropy=0
  Key Counter - hexdump(len=32): [REMOVED]
  WPA: Delay group state machine start until Beacon frames have been configured
  nl80211: Set beacon (beacon_set=0)
  nl80211: Beacon head - hexdump(len=56): 80 00 00 00 ff ff ff ff ff ff 78 32 1b 0a 0f 37 78 32 1b 0a 0f 37 00 00 00 00 00 00 00 00 00 00 64 00 11 00 00 05 74 65 73 74 31 01 08 8c 12 98 24 b0 48 60 6c 03 01 28
  nl80211: Beacon tail - hexdump(len=89): 07 06 49 4e 20 24 04 14 dd 1a 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02 7f 04 00 00 00 02 bf 0c 68 18 18 00 ff ff 00 00 ff ff 00 00 c0 05 00 28 00 fc ff dd 18 00 50 f2 02 01 01 00 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00
  nl80211: ifindex=3
  nl80211: beacon_int=100
  nl80211: dtim_period=2
  nl80211: ssid - hexdump_ascii(len=5):
  74 65 73 74 31 test1
• beacon_int=100
  nl80211: hidden SSID not in use
  nl80211: privacy=1
  nl80211: auth_algs=0x1
  nl80211: wpa_version=0x1
  nl80211: key_mgmt_suites=0x2
  nl80211: pairwise_ciphers=0x18
  nl80211: group_cipher=0x8
  nl80211: beacon_ies - hexdump(len=6): 7f 04 00 00 00 02
  nl80211: proberesp_ies - hexdump(len=6): 7f 04 00 00 00 02
  nl80211: assocresp_ies - hexdump(len=6): 7f 04 00 00 00 02
  WPA: Start group state machine to set initial keys
  WPA: group state machine entering state GTK_INIT (VLAN-ID 0)
  Get randomness: len=16 entropy=0
  GTK - hexdump(len=32): [REMOVED]
  WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0)
  wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=2 addr=0xc7868 key_idx=1 set_tx=1 seq_len=0 key_len=32
  nl80211: KEY_DATA - hexdump(len=32): [REMOVED]
  broadcast key
  nl80211: Set wlan0 operstate 0->1 (UP)
  netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=6 (IF_OPER_UP)
  Failed to set TX queue parameters for queue 0.
  Failed to set TX queue parameters for queue 1.
  Failed to set TX queue parameters for queue 2.
  Failed to set TX queue parameters for queue 3.
  wlan0: interface state COUNTRY_UPDATE->ENABLED
  wlan0: AP-ENABLED
  wlan0: Setup of interface done.
  ctrl_iface not configured!
  RTM_NEWLINK: ifi_index=12 ifname=br0 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 ()
  nl80211: Interface down (br0/br0)
  nl80211: Not the main interface (wlan0) - do not indicate interface down
  wlan0: Event INTERFACE_STATUS (5) received
  Unknown event 5
  RTM_NEWLINK: ifi_index=3 ifname=wlan0 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1003 ([UP])
  RTM_NEWLINK: ifi_index=3 ifname=wlan0 operstate=2 linkmode=0 master=12 ifi_family=0 ifi_flags=0x1003 ([UP])
  RTM_NEWLINK: ifi_index=3 ifname=wlan0 operstate=2 linkmode=0 master=12 ifi_family=0 ifi_flags=0x1003 ([UP])
  RTM_NEWLINK: ifi_index=12 ifname=br0 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 ()
  nl80211: Interface down (br0/br0)
  nl80211: Not the main interface (wlan0) - do not indicate interface down
  wlan0: Event INTERFACE_STATUS (5) received
  Unknown event 5
  RTM_NEWLINK: ifi_index=3 ifname=wlan0 master=12 operstate=2 ifi_family=7 ifi_flags=0x1003 ([UP])
  nl80211: Add ifindex 12 for bridge br0
  nl80211: Add own interface ifindex 12
  nl80211: ifindex 12 already in the list
  RTM_NEWLINK: ifi_index=12 ifname=br0 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 ()
  nl80211: Interface down (br0/br0)
  nl80211: Not the main interface (wlan0) - do not indicate interface down
  wlan0: Event INTERFACE_STATUS (5) received
  Unknown event 5
  RTM_NEWLINK: ifi_index=3 ifname=wlan0 master=12 operstate=6 ifi_family=7 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
  nl80211: Add ifindex 12 for bridge br0
  nl80211: Add own interface ifindex 12
  nl80211: ifindex 12 already in the list
  RTM_NEWLINK: ifi_index=3 ifname=wlan0 operstate=6 linkmode=0 master=12 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
  l2_packet_receive - recvfrom: Network is down
  VLAN: RTM_NEWLINK: ifi_index=3 ifname=wlan0 ifi_family=7 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
  VLAN: vlan_newlink(wlan0)
  VLAN: RTM_NEWLINK: ifi_index=3 ifname=wlan0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
  VLAN: vlan_newlink(wlan0)
  nl80211: Event message available
  nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0
  wlan0: nl80211: New scan results available
  nl80211: Scan probed for SSID ''
  nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700
  wlan0: Event SCAN_RESULTS (3) received
  VLAN: RTM_NEWLINK: ifi_index=3 ifname=wlan0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
  VLAN: vlan_newlink(wlan0)
  RTM_NEWLINK: ifi_index=3 ifname=wlan0 wext ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
  nl80211: Event message available
  nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlan0
  wlan0: nl80211: Scan trigger
  wlan0: Event SCAN_STARTED (47) received
  Unknown event 47
  nl80211: Event message available
  nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0
  wlan0: nl80211: New scan results available
  nl80211: Scan probed for SSID ''
  nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700
  wlan0: Event SCAN_RESULTS (3) received
  VLAN: RTM_NEWLINK: ifi_index=3 ifname=wlan0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
  VLAN: vlan_newlink(wlan0)
  RTM_NEWLINK: ifi_index=3 ifname=wlan0 wext ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
  nl80211: Event message available
  nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlan0
  wlan0: nl80211: Scan trigger
  wlan0: Event SCAN_STARTED (47) received
  Unknown event 47
  RTM_NEWLINK: ifi_index=3 ifname=wlan0 wext ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
  nl80211: Event message available
  nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0
  wlan0: nl80211: New scan results available
  nl80211: Scan probed for SSID ''
  nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700
  wlan0: Event SCAN_RESULTS (3) received
  VLAN: RTM_NEWLINK: ifi_index=3 ifname=wlan0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
  VLAN: vlan_newlink(wlan0)

from rtl8812au.

Pls check what is the issue.

Electrical engineering is a science which is kind of stupid to fight with. The issues which you choose to ignore plays the major role and cause unpredicted behavior which means looking into this is a complete waste of time.

There are usually enough troubles in perfect conditions.

from rtl8812au.

Debugging is key, instead doing just doing copy paste. :)
The issues you found is very minor. 8812 comes in USB 2.0 which can support 480Mbps, enough to flow data and power consumption of around ~400mA. Any way, let me figure it out and fix it.

BTW - Which board in ~$15-20 has USB 3.0 support ?

from rtl8812au.

We are already in the debug process and I find and name you two most obvious bugs :) It is wise to solve those and then move on.

My 8812au sucks up to 600mA (measured with a normal multimeter, which is not very fast which means spikes can be higher) ... enough to not work properly. Raspberry Pi: 480Mbps is used for Ethernet, Wireless, hard drive, ... That is enough??

Well, you don't exactly need USB3, but dedicated properly powered USB2 port. This is more for securing enough juice. For my experiments and debugging, I always use external powered quality USB3.0 hub which has dedicated 900mA per port. To eliminate irrelevant bugs.

The cheapest USB3 board would be Rock64 ATM but the kernel is still in a poor condition. Next is Espressobin (49USD) which is usable to some degree ... but what I would use for this is some Orangepi zero+ H5 or general purpose Orangepi PC+ (which has eMMC). They all have UASP capable dedicated USB2 ports.

from rtl8812au.

can support 480Mbps

Top USB bandwidth I was able to get from RPis was around 30-35 MiB/s, i.e. about half of that.

But that probably won't matter if you have some simple 1x1 dongle, which probably won't go beyond that anyway.

Not sure about how various network management tools report "connection speed", but it's usually plain false in my experience, i.e. "connects at 866 Mbit/s" can mean ~100 mbits/s actual throughput in iperf3.

from rtl8812au.

enough to flow data and power consumption of around ~400mA

If you'll get reboots and brownouts with decent-enough PSU, can also try adding "max_usb_current=1" to config.txt.
RPi2 was able to keep ALFA AWUS036NH working ok with that tweak and txpower cranked up to 40-50 (on patched regdb).

from rtl8812au.

Oh, also, one rather simple way to work around most such power limitations is to cut usb extender cable and solder power wires there to go directly to psu instead of usb port.

from rtl8812au.

Let me try external hub or setting up max_usb_current=1 ( I think its already set), just make sure power is not the issue. But looking at HOSTAPD logs, it doesn't look like power issue.

from rtl8812au.

My end goal is to make Wifi extender for AC signals. Means bridging Wlan0 to Wlan1 .

from rtl8812au.

Top USB bandwidth I was able to get from RPis was around 30-35 MiB/s, i.e. about half of that.
"connects at 866 Mbit/s" can mean ~100 mbits/s actual throughput in iperf3.

For reference. Iperf3 goes around 200 mbit/s with 8812au and 260 mbit/s with Compex VX600 (mPCI). In both cases client is Notebook with Intel 7260 dual AC stream.

2 x 1x1 AC WLAN is estimated little over 200mbit/s ... so this should work if used solo for the purpose of bridging and if you power properly while dual AC stream wont go.

from rtl8812au.

Guys - I tried external self power hub but still getting same issue. Can anyone post working HOSTAPD conf file with this driver.

from rtl8812au.

Actually, wrt bridging, pretty sure it's bad news - 8812au (at least 5.1.5 I've tried) doesn't support 4addr mode (i.e. can't send packets through the B -> C bridge with two extra A -> D macs inside).
Maybe fixed in 5.2.9, though I didn't see it in the changelog.
Would be happy to be proven wrong on this btw, iirc only checked whether knob works via "iw" and module parameters, didn't find mode available in either.

from rtl8812au.

working HOSTAPD conf file

I think I have one for ac mode only here - https://github.com/mk-fg/rtl8812au#performance

from rtl8812au.

I have a simple way to setup the AP mode for rtl8812au，just install create_ap, it's a script that creates a NATed or Bridged WiFi Access Point. With it, I can get away from those annoying configure parameters. It worth a try on it. The address is : https://github.com/oblique/create_ap

from rtl8812au.

Hi all, for research purposes, we are using AP mode for creating an AP that hosts a number of “virtual APs”, and each one must have its own MAC address.

For that aim, the AP should send Wi-Fi ACKs when receiving a frame from any of these “virtual MAC” addresses.

This can already be done with ath9k (https://github.com/Wi5/odin-wi5/tree/master/odin-patch-driver-ath9k), making use of the “debug” functionalities of the ath9k driver. We use the bitmask for that.

But we don’t know if we would be able to do something similar with the RTL8812 driver. If you have any clues, they will be more than welcome.

from rtl8812au.