Ahh! TIL. Thank you!
I am able to achieve similar speed as when WED was enabled.
Yes, packet steering is enabled with RPS set to standard.
I previously posted about this issue and wanted to share my recent troubleshooting (summarized by chatgpt, apologies) to see if anyone has any ideas for further diagnosing.
Iām seeing a consistent Wi-Fi downlink throughput cap (~450ā520 Mbps) on a Belkin RT3200 (MT7622 + mt7915) running OpenWrt 24.10.4 , while uplink reaches ~700ā800 Mbps . I do not recall this issue on OpenWrt 23.05 , where down/up were roughly symmetric.
System details
OpenWrt 24.10.4, r28959-29397011cc, Linux 6.6.110 aarch64
Wireless: 5 GHz, channel 149 (non-DFS) , 80 MHz
Security: WPA2-PSK (CCMP)
Client: Windows, Intel Wi-Fi 6E AX211
Symptoms
Client ā AP (uplink): ~700ā800 Mbps (iperf3)
AP ā client (downlink): ~450ā520 Mbps
Same behavior with:
internet speedtests
local iperf3
CPU not pegged, RSSI and PHY rates look good
Wi-Fi-only reproduction (no VLAN / bridge path)
Windows runs iperf3 server, AP runs client:
Windows (Wi-Fi):
iperf3.exe -s -B <wifi_ip>
AP:
iperf3 -c <wifi_ip> -P 4 -t 30
This is AP ā Wi-Fi client only (no Ethernet/DSA/bridge involved) and still caps ~500 Mbps down while uplink is higher.
iw station observations
During downlink testing:
High PHY rates, e.g. HE-MCS 10/11, 80 MHz, 2SS
Low retries/failures (not interference-limited)
Repeatedly see:
rx bitrate: 24.0 MBit/s
which appears to indicate low-rate ACK/control traffic and aligns with TCP downlink being limited despite high PHY.
What Iāve already ruled out
VLAN / bridge: APāclient iperf reproduces issue; VLAN filtering on/off and WAN/LAN swaps made no difference
CPU / IRQ / offload: IRQ pinning, RPS/XPS tried; no impact
RF basics: clean non-DFS channel, WPA2-only, good signal
Client fallback: iperf bound to Wi-Fi IP; Ethernet disabled during tests
Suspected cause
Given the directional nature (downlink only) , Wi-Fi-only reproduction, good PHY + low retries, and my experience that 23.05 did not behave this way , this looks like a mt76/mt7915 regression or behavior change in newer kernels (5.15 ā 6.6), possibly around HE/ACK handling or power-save interactions with Intel AX2xx clients.
Questions
Has anyone else seen ~500 Mbps APāclient caps on mt7915 with 24.10 / kernel 6.6 ?
Are there known mt76 regressions affecting downlink TCP / ACK pacing , especially with Intel AX211?
Any recommended snapshot, patch, or known workaroundāor is 23.05 just a more stable choice for mt7915?
Happy to provide iw dev station dump, wireless config, or test specific snapshots if helpful.
Thanks.
1 Like
Thereās something odd on your config.
I have had the same speeds since I got this router and started using OpenWRT since v22.x, then upgraded to all 23.05.x releases, all the 24.10.x releases and now Iām on 25.12.0-rc2.
But, in my case, I do reach speedtests of about 650-700 Mbps, sometimes 750, and upload speeds of 890, 900 Mbps, consistent on what you mention.
However, running iperf3 between my laptop and another device behind the router (to avoid any CPU overhead), I do get consistent 900ish Mbps on both download and upload. Only on internet speed tests is that I get around 700 Mbps.
I have tested with WED enabled and disabled and decided to keep it disabled and itās stable. Of course HW Flow Offloading and Packet steering enabled with standard flows (none).
I do use 160MHz, tho. Donāt know if that makes a difference. In my laptop, the link speed is 2401Mbps, whereas on 80MHz, the link speed is 1200Mbps.
Thanks for the reply. In the /etc/config/wireless is:
...
config wifi-device 'radio1'
option type 'mac80211'
option path '1a143000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
option band '5g'
option country 'US'
option cell_density '1'
option htmode 'HE80'
option channel '149'
option log_level '2'
config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option encryption 'psk2'
option ieee80211r '1'
option ft_over_ds '0'
option ft_psk_generate_local '1'
option time_advertisement '2'
option time_zone 'GMT0'
option ieee80211k '1'
option bss_transition '1'
...
Looks similar to mine (FT options and such), but I use 160MHz, on channel 36 for my router, and 104 for my dumb AP.
How far are you when doing the tests? The best speeds are achieved only by being very close to the router. WiFi is tricky.
In any case, you should get at least 600-650Mbps download. Less than that is odd.
quarky
January 8, 2026, 11:09pm
6876
Not recommended to test with the AP itself. Should test as below instead:
iperf3 server < - > RT3200 < - > iperf3 client
This!
In my case I get around 900 Mbps in iperf3, but thereās no way to achieve this in internet speed tests on WiFi. Only up to 700ish. I can achieve it wired.
Do you have any tips to get more WiFi download speed?
dalutou
January 9, 2026, 3:40am
6878
My Linksys E8450 runs OpenWRT 25.12.0-rc2 with Hardware Flow Offloading on, 80Mhz.
Iperf3 test:
Server: LAN (Wired), a PC on Debian, 192.168.200.3.
Client: LAN (Wi-Fi 6 1200Mbps) , a Minibox PC on Windows 11. (There is a bookshelf between the router and the client)
# iperf3.exe -c 192.168.200.3 -P 10
[SUM] 0.00-10.01 sec 714 MBytes 598 Mbits/sec sender
[SUM] 0.00-10.03 sec 693 MBytes 580 Mbits/sec receiver
It's basically around 600Mbps, sometimes 700Mbps.
1 Like
This is my iperf3 using my laptop with a Qualcomm FastConnect 6900 connected to my RT3200 router and my other RT3200 dumb AP as a client (to test the WiFi throughput of the router):
root@CharlieExt:~# iperf3 -c 192.168.1.226
Connecting to host 192.168.1.226, port 5201
[ 5] local 192.168.1.2 port 55284 connected to 192.168.1.226 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 103 MBytes 860 Mbits/sec 0 2.11 MBytes
[ 5] 1.00-2.00 sec 110 MBytes 918 Mbits/sec 0 2.11 MBytes
[ 5] 2.00-3.00 sec 108 MBytes 907 Mbits/sec 0 2.11 MBytes
[ 5] 3.00-4.00 sec 106 MBytes 894 Mbits/sec 0 2.11 MBytes
[ 5] 4.00-5.00 sec 107 MBytes 895 Mbits/sec 0 2.11 MBytes
[ 5] 5.00-6.00 sec 107 MBytes 901 Mbits/sec 0 2.11 MBytes
[ 5] 6.00-7.00 sec 108 MBytes 903 Mbits/sec 0 2.11 MBytes
[ 5] 7.00-8.00 sec 108 MBytes 909 Mbits/sec 0 2.11 MBytes
[ 5] 8.00-9.00 sec 106 MBytes 890 Mbits/sec 0 2.11 MBytes
[ 5] 9.00-10.00 sec 108 MBytes 903 Mbits/sec 0 2.11 MBytes
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.05 GBytes 899 Mbits/sec 0 sender
[ 5] 0.00-10.01 sec 1.04 GBytes 896 Mbits/sec receiver
iperf Done.
And the reverse test (upload from the AP to the laptop):
root@CharlieExt:~# iperf3 -c 192.168.1.226 -R
Connecting to host 192.168.1.226, port 5201
Reverse mode, remote host 192.168.1.226 is sending
[ 5] local 192.168.1.2 port 58818 connected to 192.168.1.226 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 104 MBytes 869 Mbits/sec
[ 5] 1.00-2.00 sec 106 MBytes 892 Mbits/sec
[ 5] 2.00-3.00 sec 107 MBytes 900 Mbits/sec
[ 5] 3.00-4.00 sec 111 MBytes 927 Mbits/sec
[ 5] 4.00-5.00 sec 111 MBytes 930 Mbits/sec
[ 5] 5.00-6.00 sec 107 MBytes 895 Mbits/sec
[ 5] 6.00-7.00 sec 111 MBytes 929 Mbits/sec
[ 5] 7.00-8.00 sec 111 MBytes 931 Mbits/sec
[ 5] 8.00-9.00 sec 108 MBytes 909 Mbits/sec
[ 5] 9.00-10.00 sec 109 MBytes 917 Mbits/sec
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 1.06 GBytes 912 Mbits/sec sender
[ 5] 0.00-10.00 sec 1.06 GBytes 910 Mbits/sec receiver
iperf Done.
Pretty much symmetrical.
But running any speed test, I get up to 690-700ish Mbps in downloads, and around 900Mbps in uploads. Running internet speed tests wired, does give me aroung 900 Mbps symmetrical.
eginnc
January 9, 2026, 3:31pm
6880
I get line rate (low 900ās) over WiFi in the same room as my RT3200 on channel 52 with 80Mz width.
I have never had the need to experiment with 160 MHz width, but I recall reading on the internet (Hah! Now thereās a reliable source reference!) that there is a trade-off between speed at range and channel width. Sorry I canāt give you personal experience, but it might be worth an experiment to see if 80 MHz is as good as (perhaps better?) 160 MHz at longer distances from the AP. 80 MHz makes it easier to avoid channel frequency overlap interference with multiple APās too.
eginnc
January 9, 2026, 3:37pm
6881
Nvrmnd - I see you are already getting near line rate over WiFi with iperf3 now.
Yeah, wireless is fine through iperf3. Internet speed tests are the problem where I get around 650-700 Mbps wireless but around 900 wired. Those are downloads. Uploads are fine on both wireless and wired.
1 Like
The same with WED enabled or disabled.
So, it sounds like I am not alone in this now. Something is happening in the AP->wifi_client download and does not appear to be overloaded cpu.
Could it be that what we are seeing is the same as is reported in the mt7915 driver:
opened 03:23PM - 27 May 25 UTC
So, I'm currently on a MT7981 device with a 2x2 spatial streams. Everything is w⦠orking very well, except that the download speeds are WAY slower than upload speeds. During iperf3 tests (also does apply to real-world tests using Ookla speedtest):
- Average upload speed: 1.59 Gbps
- Average download speed: 850Mbps
Things that I have tried:
- Patching the driver to load the proprietary .bin firmware from Mediatek.
- Playing with options in /etc/config/wireless.
- Testing with UDP on iperf3 to discard any TCP-specific issue.
- Monitoring the TX bitrates during tests, they are stable at 2.4Gbps, using MCS 10/12 usually.
I'm 100% sure that it's a driver/firmware issue. With the original firmware, which is a private fork of OpenWrt, it gets the expected download speeds. Sadly, that version doesn't have a way to configure many things via `uci`, and therefore is not suitable for me.
The firmware has been tested on multiple devices and the result is the same on each one, that's why I'm 100% sure that it's an issue with the firmware. Flashing the old image also returns the correct behavior back.
The current loaded modules are:
```
cfg80211 319488 4 mt7915e,mt76_connac_lib,mt76,mac80211
mac80211 614400 3 mt7915e,mt76_connac_lib,mt76
mt76 77824 2 mt7915e,mt76_connac_lib
mt76_connac_lib 49152 1 mt7915e
mt7915e 245760 0
```
Some data from the tests:
#### Upload
```bash
$ iperf3 --bind-dev wlan0 -c 192.168.1.1 -t 86400 -P4
Connecting to host 192.168.1.1, port 5201
[ 5] local 192.168.1.229 port 34484 connected to 192.168.1.1 port 5201
[ 7] local 192.168.1.229 port 34488 connected to 192.168.1.1 port 5201
[ 9] local 192.168.1.229 port 34490 connected to 192.168.1.1 port 5201
[ 11] local 192.168.1.229 port 34496 connected to 192.168.1.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 67.1 MBytes 563 Mbits/sec 0 1.27 MBytes
[ 7] 0.00-1.00 sec 31.5 MBytes 264 Mbits/sec 0 1.26 MBytes
[ 9] 0.00-1.00 sec 74.4 MBytes 624 Mbits/sec 0 1.79 MBytes
[ 11] 0.00-1.00 sec 49.0 MBytes 411 Mbits/sec 0 1.28 MBytes
[SUM] 0.00-1.00 sec 222 MBytes 1.86 Gbits/sec 0
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 1.00-2.00 sec 54.1 MBytes 454 Mbits/sec 0 1.27 MBytes
[ 7] 1.00-2.00 sec 51.0 MBytes 428 Mbits/sec 0 1.26 MBytes
[ 9] 1.00-2.00 sec 53.6 MBytes 450 Mbits/sec 0 1.79 MBytes
[ 11] 1.00-2.00 sec 53.4 MBytes 448 Mbits/sec 0 1.28 MBytes
[SUM] 1.00-2.00 sec 212 MBytes 1.78 Gbits/sec 0
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 2.00-3.00 sec 52.4 MBytes 439 Mbits/sec 0 1.27 MBytes
[ 7] 2.00-3.00 sec 50.5 MBytes 424 Mbits/sec 0 1.26 MBytes
[ 9] 2.00-3.00 sec 52.4 MBytes 439 Mbits/sec 0 1.79 MBytes
[ 11] 2.00-3.00 sec 53.9 MBytes 452 Mbits/sec 0 1.28 MBytes
[SUM] 2.00-3.00 sec 209 MBytes 1.75 Gbits/sec 0
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 3.00-4.00 sec 52.6 MBytes 441 Mbits/sec 0 1.27 MBytes
[ 7] 3.00-4.00 sec 49.2 MBytes 413 Mbits/sec 0 1.26 MBytes
[ 9] 3.00-4.00 sec 52.9 MBytes 443 Mbits/sec 0 1.79 MBytes
[ 11] 3.00-4.00 sec 52.1 MBytes 437 Mbits/sec 0 1.28 MBytes
[SUM] 3.00-4.00 sec 207 MBytes 1.73 Gbits/sec 0
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 4.00-5.00 sec 53.2 MBytes 447 Mbits/sec 0 1.27 MBytes
[ 7] 4.00-5.00 sec 51.8 MBytes 434 Mbits/sec 0 1.26 MBytes
[ 9] 4.00-5.00 sec 57.5 MBytes 482 Mbits/sec 0 1.79 MBytes
[ 11] 4.00-5.00 sec 54.2 MBytes 455 Mbits/sec 0 1.28 MBytes
[SUM] 4.00-5.00 sec 217 MBytes 1.82 Gbits/sec 0
^C- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 5.00-5.89 sec 44.6 MBytes 422 Mbits/sec 0 1.27 MBytes
[ 7] 5.00-5.89 sec 44.1 MBytes 417 Mbits/sec 0 1.26 MBytes
[ 9] 5.00-5.89 sec 50.4 MBytes 476 Mbits/sec 0 1.79 MBytes
[ 11] 5.00-5.89 sec 44.6 MBytes 422 Mbits/sec 0 1.28 MBytes
[SUM] 5.00-5.89 sec 184 MBytes 1.74 Gbits/sec 0
```
#### Download
```bash
$ iperf3 --bind-dev wlan0 -c 192.168.1.1 -t 86400 -P4 --reverse
Connecting to host 192.168.1.1, port 5201
Reverse mode, remote host 192.168.1.1 is sending
[ 5] local 192.168.1.229 port 58384 connected to 192.168.1.1 port 5201
[ 7] local 192.168.1.229 port 58386 connected to 192.168.1.1 port 5201
[ 9] local 192.168.1.229 port 58396 connected to 192.168.1.1 port 5201
[ 11] local 192.168.1.229 port 58402 connected to 192.168.1.1 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 29.9 MBytes 251 Mbits/sec
[ 7] 0.00-1.00 sec 27.8 MBytes 233 Mbits/sec
[ 9] 0.00-1.00 sec 21.2 MBytes 178 Mbits/sec
[ 11] 0.00-1.00 sec 21.9 MBytes 183 Mbits/sec
[SUM] 0.00-1.00 sec 101 MBytes 845 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 1.00-2.00 sec 27.4 MBytes 230 Mbits/sec
[ 7] 1.00-2.00 sec 24.2 MBytes 203 Mbits/sec
[ 9] 1.00-2.00 sec 24.4 MBytes 204 Mbits/sec
[ 11] 1.00-2.00 sec 24.2 MBytes 203 Mbits/sec
[SUM] 1.00-2.00 sec 100 MBytes 841 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 2.00-3.00 sec 26.1 MBytes 219 Mbits/sec
[ 7] 2.00-3.00 sec 24.2 MBytes 203 Mbits/sec
[ 9] 2.00-3.00 sec 24.2 MBytes 203 Mbits/sec
[ 11] 2.00-3.00 sec 24.2 MBytes 203 Mbits/sec
[SUM] 2.00-3.00 sec 98.9 MBytes 829 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 3.00-4.00 sec 26.5 MBytes 222 Mbits/sec
[ 7] 3.00-4.00 sec 24.2 MBytes 203 Mbits/sec
[ 9] 3.00-4.00 sec 24.4 MBytes 204 Mbits/sec
[ 11] 3.00-4.00 sec 24.0 MBytes 201 Mbits/sec
[SUM] 3.00-4.00 sec 99.1 MBytes 832 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 4.00-5.00 sec 24.9 MBytes 209 Mbits/sec
[ 7] 4.00-5.00 sec 24.1 MBytes 202 Mbits/sec
[ 9] 4.00-5.00 sec 24.8 MBytes 208 Mbits/sec
[ 11] 4.00-5.00 sec 24.0 MBytes 201 Mbits/sec
[SUM] 4.00-5.00 sec 97.8 MBytes 820 Mbits/sec
^C- - - - - - - - - - - - - - - - - - - - - - - - -
[ 5] 5.00-5.31 sec 7.25 MBytes 199 Mbits/sec
[ 7] 5.00-5.31 sec 7.25 MBytes 199 Mbits/sec
[ 9] 5.00-5.31 sec 8.12 MBytes 223 Mbits/sec
[ 11] 5.00-5.31 sec 7.38 MBytes 203 Mbits/sec
[SUM] 5.00-5.31 sec 30.0 MBytes 825 Mbits/sec
```
#### iw phy1 info
<details>
<summary>iw info</summary>
```
Wiphy phy1
wiphy index: 1
max # scan SSIDs: 4
max scan IEs length: 2190 bytes
max # sched scan SSIDs: 0
max # match sets: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Device supports T-DLS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CCMP-256 (00-0f-ac:10)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
* CMAC (00-0f-ac:6)
* CMAC-256 (00-0f-ac:13)
* GMAC-128 (00-0f-ac:11)
* GMAC-256 (00-0f-ac:12)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
* P2P-client
* P2P-GO
Band 2:
Capabilities: 0x9ff
RX LDPC
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 2 usec (0x04)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x339a59f6):
Max MPDU length: 11454
Supported Channel Width: 160 MHz
RX LDPC
short GI (80 MHz)
short GI (160/80+80 MHz)
TX STBC
SU Beamformer
SU Beamformee
MU Beamformer
MU Beamformee
RX antenna pattern consistency
TX antenna pattern consistency
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
VHT extended NSS: supported
HE Iftypes: managed
HE MAC Capabilities (0x08011a000040):
+HTC HE Supported
Trigger Frame MAC Padding Duration: 2
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x4c70ce926d12f3164e3f00):
HE40/HE80/5GHz
HE160/5GHz
242 tone RUs/5GHz
Device Class: 1
LDPC Coding in Payload
HE SU PPDU with 1x HE-LTF and 0.8us GI
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformer
SU Beamformee
Beamformee STS <= 80Mhz: 3
Beamformee STS > 80Mhz: 3
Sounding Dimensions <= 80Mhz: 2
Sounding Dimensions > 80Mhz: 2
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered CQI Feedback
Partial Bandwidth Extended Range
Partial Bandwidth DL MU-MIMO
PPE Threshold Present
Power Boost Factor ar
HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
Max NC: 2
20MHz in 40MHz HE PPDU 2.4GHz
20MHz in 160/80+80MHz HE PPDU
80MHz in 160/80+80MHz HE PPDU
DCM Max BW: 1
Longer Than 16HE SIG-B OFDM Symbols
Non-Triggered CQI Feedback
TX 1024-QAM
RX 1024-QAM
RX Full BW SU Using HE MU PPDU with Compression SIGB
RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE RX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
HE Iftypes: AP
HE MAC Capabilities (0x00051a081044):
+HTC HE Supported
TWT Responder
BSR
OM Control
Maximum A-MPDU Length Exponent: 3
BQR
A-MSDU in A-MPDU
OM Control UL MU Data Disable RX
HE PHY Capabilities: (0x0c20ce926f12afd0000c00):
HE40/HE80/5GHz
HE160/5GHz
LDPC Coding in Payload
NDP with 4x HE-LTF and 3.2us GI
STBC Tx <= 80MHz
STBC Rx <= 80MHz
Full Bandwidth UL MU-MIMO
Partial Bandwidth UL MU-MIMO
DCM Max Constellation: 2
DCM Max Constellation Rx: 2
SU Beamformer
SU Beamformee
MU Beamformer
Beamformee STS <= 80Mhz: 3
Beamformee STS > 80Mhz: 3
Sounding Dimensions <= 80Mhz: 2
Sounding Dimensions > 80Mhz: 2
Codebook Size SU Feedback
Codebook Size MU Feedback
Triggered SU Beamforming Feedback
Triggered MU Beamforming Feedback
Partial Bandwidth Extended Range
PPE Threshold Present
Max NC: 2
STBC Tx > 80MHz
STBC Rx > 80MHz
TX 1024-QAM
RX 1024-QAM
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE RX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
PPE Threshold 0x39 0x1c 0xc7 0x71 0x1c 0x07
HE Iftypes: mesh point
HE MAC Capabilities (0x00011a000040):
+HTC HE Supported
OM Control
Maximum A-MPDU Length Exponent: 3
A-MSDU in A-MPDU
HE PHY Capabilities: (0x0c200c0000000000008000):
HE40/HE80/5GHz
HE160/5GHz
LDPC Coding in Payload
STBC Tx <= 80MHz
STBC Rx <= 80MHz
HE RX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set <= 80 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE RX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
HE TX MCS and NSS set 160 MHz
1 streams: MCS 0-11
2 streams: MCS 0-11
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
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.0 MHz [36] (17.0 dBm)
* 5200.0 MHz [40] (17.0 dBm)
* 5220.0 MHz [44] (17.0 dBm)
* 5240.0 MHz [48] (17.0 dBm)
* 5260.0 MHz [52] (24.0 dBm) (radar detection)
* 5280.0 MHz [56] (24.0 dBm) (radar detection)
* 5300.0 MHz [60] (24.0 dBm) (radar detection)
* 5320.0 MHz [64] (24.0 dBm) (radar detection)
* 5360.0 MHz [72] (disabled)
* 5380.0 MHz [76] (disabled)
* 5400.0 MHz [80] (disabled)
* 5420.0 MHz [84] (disabled)
* 5440.0 MHz [88] (disabled)
* 5460.0 MHz [92] (disabled)
* 5500.0 MHz [100] (24.0 dBm) (radar detection)
* 5520.0 MHz [104] (24.0 dBm) (radar detection)
* 5540.0 MHz [108] (24.0 dBm) (radar detection)
* 5560.0 MHz [112] (24.0 dBm) (radar detection)
* 5580.0 MHz [116] (24.0 dBm) (radar detection)
* 5600.0 MHz [120] (24.0 dBm) (radar detection)
* 5620.0 MHz [124] (24.0 dBm) (radar detection)
* 5640.0 MHz [128] (24.0 dBm) (radar detection)
* 5660.0 MHz [132] (24.0 dBm) (radar detection)
* 5680.0 MHz [136] (24.0 dBm) (radar detection)
* 5700.0 MHz [140] (24.0 dBm) (radar detection)
* 5720.0 MHz [144] (24.0 dBm) (radar detection)
* 5745.0 MHz [149] (25.0 dBm)
* 5765.0 MHz [153] (25.0 dBm)
* 5785.0 MHz [157] (25.0 dBm)
* 5805.0 MHz [161] (25.0 dBm)
* 5825.0 MHz [165] (25.0 dBm)
* 5845.0 MHz [169] (disabled)
* 5865.0 MHz [173] (disabled)
* 5885.0 MHz [177] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* tdls_mgmt
* tdls_oper
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* testmode
* connect
* disconnect
* channel_switch
* set_qos_map
* set_multicast_to_unicast
* set_sar_specs
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports low priority scan.
Device supports scan flush.
Device supports AP scan.
Device supports per-vif TX power setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Device supports active monitor (which will ACK incoming frames)
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
Device supports configuring vdev MAC-addr on create.
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
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
* mesh point: 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
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xb0 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
Supported extended features:
* [ VHT_IBSS ]: VHT-IBSS
* [ RRM ]: RRM
* [ BEACON_RATE_LEGACY ]: legacy beacon rate setting
* [ BEACON_RATE_HT ]: HT beacon rate setting
* [ BEACON_RATE_VHT ]: VHT beacon rate setting
* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ ACK_SIGNAL_SUPPORT ]: ack signal level support
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
* [ SCAN_RANDOM_SN ]: use random sequence numbers in scans
* [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
* [ CAN_REPLACE_PTK0 ]: can safely replace PTK 0 when rekeying
* [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
* [ STA_TX_PWR ]: TX power control per station
* [ AQL ]: Airtime Queue Limits (AQL)
* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
* [ DEL_IBSS_STA ]: deletion of IBSS station support
* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
* [ FILS_DISCOVERY ]: FILS discovery frame transmission support
* [ UNSOL_BCAST_PROBE_RESP ]: unsolicated broadcast probe response transmission support
* [ BEACON_RATE_HE ]: HE beacon rate support (AP/mesh)
* [ BSS_COLOR ]: BSS coloring support
* [ POWERED_ADDR_CHANGE ]: can change MAC address while up
```
</details>
EDIT: Others having similar problems here and not present on 23.05.5
All right, I downgraded my e8450 back to 23.05.x series, which seem to work better for me (speeds consistently above 500 mbps both ways on my chromebook, above 400 mbps both ways on my old macbook, and about 400 down / 200 up on my pixel 6 phone). The intermittent slowdowns I was seeing with 24.10.0-rc4 are gone. For the record, 24.10.0-rc5 didn't seem to help either.
I'm going to record my downgrade procedure in case it helps someone else. The preconditions for this procedure are that I had prā¦
quarky
January 11, 2026, 12:15am
6886
Iām currently using a GL-iNet MT6000, but it is essentially a MT7915E, so it should be similar to the RT3200/E8450.
Iām able to get line speed for download (800Mbps) when tested with my iPhone with Speediest.Net apps, when Iām really close to the AP. It looks about right to me since my iPhone max PHY speed is 1200Mbps. With AX router, since max PHY speed is only 866Mbps, my iPhone can only get around 600Mbps on a good day.
My MT6000 is running on a master tree build from around early October 2025.
Are you using snapshot/master or the stable releases?
I prefer snapshot since the mt76 drivers are most current.
Edit: To add on, sometimes turning down the APās TX power might help in signal stability as it might result is a less noisy environment.
RSpliet
January 11, 2026, 2:16pm
6887
Itās been a few months, but I thought Iād follow up on the issue I had since october/november with wifi not working on snapshot. A closed issue on github encouraged me to retry with todayās snapshot. Initially wifi didnāt work, just like before. However, after re-creating my wifi networks on radio2 and radio3 (which look like clones of radio0 and radio1), things now work. Even after a reboot my network comes up. So, hooray I can make it work and I can now be on an up to date software stack. But also: why are there two sets of radios, and why am I obliged to use radio2 and radio3 since some change in october?