Low Wifi 5G speed with TP-Link Archer C6 v3

fwiw, if you want faster wifi speeds, you may need to consider installing a separate wireless access point running OEM firmware for maximum performance. OpenWrt wireless is often inferior to OEM firmwares in my experience.

For my Xiaomi 4A Gigabit with 21.02.x, I recall routed speeds from WAN to ethernet LAN were

Routed speeds to Intel 7026ac 802.11ac 2x2 wireless (80MHz) client

Here it is: https://pastebin.com/k0Vr0Dfp

Not really, there is a difference between the advertized data link rate - and the effective throughput you can get at your clients. The advertized top speeds of modern routers are given with all rf chains used (3x3, 4x4, up to 8x8 for wifi6), but your clients are mostly 2x2 (notebooks, good phones), 1x1 (IoT, cheap phones, USB cards, cheap tablets, cheap notebooks, ...) or maybe 3x3 for very high-end notebooks. With 802.11ac, 2x2 (@80 MHz channel bandwidth) leaves you with 866 MBit/s link rate at most, which -in practice- allows you speeds (rule of thumb, roughly half) around 300-350 MBit/s, maybe 400 MBit/s under ideal circumstances.

If you want more than that, you either need to increase the number of rf chains (~antennas) on both client and AP - or move to 802.11ax/ wifi6.

2 Likes

Look at this :

IMHO, stick to the channel 36, with a channel width of 160Mhz.

If I chose 160Mhz, the interface doesn't even work. I cannot see the wifi in any of my devices, including a Samsung S22+ (Wi-Fi 802.11 a/b/g/n/ac/ax 2.4G+5GHz+6GHz, HE160, MIMO, 1024-QAM - Up to 2.4Gbps Download / Up to 2.4Gbps Upload)

Thanks for the picture. It helps me to understand how it works.

Also, thank you @slh for your explanation. But a Samsung S22+ should be able to use the full 160Mhz if it would be shown, right?

160 MHz rarely works, half of your bandwidth always overlaps with the DFS range, meaning you're very suspectible to interference and radar events (and false radar events, caused by interference from your neighbours). Unless you're in a shielded rf lab, live in the sticks far away from airports, ports, military, weather stations and neighbours or can use the 6 GHz band (even shorter range, fewer competition), you'd be better of with 80 MHz channels.

The more you push it (160 MHz), the more you challenge hardware, firmware and drivers, some will stand the pressure better than others.

1 Like

in my case, with a totolink a8000ru, i set channel 36, width 160Mhz. My phone is a samsung S20, and it connects using 80Mhz. not 160Mhz but at least it can connects and it works...
if your radio doesn't even want to start, then there must be a bad setting combination somewhere ?

So your device says :

                VHT Capabilities (0x338001f8):
                        Max MPDU length: 3895
                        Supported Channel Width: 160 MHz, 80+80 MHz
                        RX LDPC
                        short GI (80 MHz)
                        short GI (160/80+80 MHz)

                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] (20.0 dBm) (radar detection)
                        * 5280 MHz [56] (20.0 dBm) (radar detection)
                        * 5300 MHz [60] (20.0 dBm) (radar detection)
                        * 5320 MHz [64] (20.0 dBm) (radar detection)
                        * 5500 MHz [100] (23.0 dBm) (radar detection)
                        * 5520 MHz [104] (23.0 dBm) (radar detection)
                        * 5540 MHz [108] (23.0 dBm) (radar detection)
                        * 5560 MHz [112] (23.0 dBm) (radar detection)
                        * 5580 MHz [116] (23.0 dBm) (radar detection)
                        * 5600 MHz [120] (23.0 dBm) (radar detection)
                        * 5620 MHz [124] (23.0 dBm) (radar detection)
                        * 5640 MHz [128] (23.0 dBm) (radar detection)
                        * 5660 MHz [132] (23.0 dBm) (radar detection)
                        * 5680 MHz [136] (23.0 dBm) (radar detection)
                        * 5700 MHz [140] (23.0 dBm) (radar detection)
                        * 5720 MHz [144] (13.0 dBm) (radar detection)
                        * 5745 MHz [149] (13.0 dBm)
                        * 5765 MHz [153] (13.0 dBm)
                        * 5785 MHz [157] (13.0 dBm)
                        * 5805 MHz [161] (13.0 dBm)
                        * 5825 MHz [165] (13.0 dBm)
                        * 5845 MHz [169] (13.0 dBm)
                        * 5865 MHz [173] (13.0 dBm)

Can you force Channel 100 then ?

you can try to troubleshot your problem with this free tool : Acrylic wifi home

it will show you in the chan column how many channels are used. 4 channels = 80Mhz, 8 channels = 160Mhz.

Thanks a lot for the help. I've tried all the combinations of channels with 160Mhz to no avail. Maybe with further fixes to drivers something more can be achieved. To be honest, the speed is lower than with the old router, but the perceived speed on my smartphone is better, so I'm ok with it.

I could try with future versions of OpenWRT if 160Mhz is available, but maybe as @slh said, it's not worth it. If I try it in the future and it works better, I'll update this thread.

Thanks!

C6v3 doesn't support 160mhz or dfs channels even with the stock firmware, so maybe a hardware limitation?

It says it supports 863Mhz on the 5Ghz band.

867 Mbps :sweat_smile:

image

And from the Spec page :


So that's true, the device doesn't support 160Mhz channel width.

2 Likes

Ahhh! Then the problem is with OpenWRT that should not allow 160Mhz. Thanks for finding it for me.

Anyways, @slh said this:

"leaves you with 866 MBit/s link rate at most, which -in practice- allows you speeds (rule of thumb, roughly half) around 300-350 MBit/s, maybe 400 MBit/s under ideal circumstances"

And that's true: I get from 300 to 450 MBit/s. But why is that?

but according to the command output : iw list
the driver says :

                VHT Capabilities (0x338001f8):
                        Max MPDU length: 3895
                        Supported Channel Width: 160 MHz, 80+80 MHz
                        RX LDPC
                        short GI (80 MHz)
                        short GI (160/80+80 MHz)

it talks about 160Mhz, why ??

I don't know why. This is what I see:

maybe this issue should be reported here : https://github.com/openwrt/mt76/issues

EDIT :
Sorry, i opened my own topic, i don't want to hijack this one as my router is different.

Maybe the OpenWRT frontend (LuCI) takes the information from there...

As @slh mentioned, there is a difference between "theoretical" and "real-world" speed.

Run cat /etc/config/wireless

Redact the passwords in the "option key" sections.

Post the results in preformatted text, by using the icon highlighted in red...

OpenWRT Posting Icons

As you can see in this graphic, channel 36 at 160 MHz overlaps with 14 other channels -

root@OpenWrt:~# cat /etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option path '1e140000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
        option band '2g'
        option htmode 'HT20'
        option channel 'auto'
        option cell_density '0'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'MIWIFI_2G'
        option encryption 'psk-mixed'
        option key 'xxxxx'

config wifi-device 'radio1'
        option type 'mac80211'
        option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0'
        option band '5g'
        option cell_density '0'
        option htmode 'VHT80'
        option channel 'auto'
        option txpower '10'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'MIWIFI_5G'
        option key 'xxxxxx'
        option encryption 'psk-mixed'