I think there was a change so if it's not set it will be set to a random number between 1-63.
In reference to the directions linked here
I think its important to know what should actually be done.
ok so if i understand he work only on snapshot not 22.03 ?
@thorsten97 @andyrichardson You'd probably get a better gain if you'd look for antennas without RP-SMA connector (just straight cable). I think might be some loss on the connector and pigtail both. Might be that even soldering pigtail after removal of U.FLs would be better 
So my question is with wed enabled will it work with a load balance - round robin? or am I expecting to much here? I'm trying to get above 1.03 Gbits/sec over wifi.
Using latest snapshot with bridge and WED enabled. Dumb ap setup with all necessary tweaks based on the wiki. iperf3 test in same spot will have 300+ Mbps download, but 10 Mbps or often 0 Mbps upload with two walls in between AP and client. Download seems normal, but upload is off. Any suggestion?
Does this happen to be an Apple/Broadcom client?
yes. iPhone and MacBook. Seems like only happen when in distance. Move closer upload and download both are fine.
802.11ax worse than 802.11ac with mt76 driver? This is a known issue, but it seems to be an Apple/Broadcom issue as it’s been seen across mediatek and Qualcomm chips. Setting the AP to 802.11ac is a temporary “fix”.
I see. thanks
I "think" that Apple devices don't have the problem using AX under the Belkin or Linksys stock firmware, right? Please let me know if I'm wrong.
I never tried the stock firmware. We have several new iPhones and iPads connecting and working just fine on a recent snapshot using the opensource driver for reference.
no, i don't have this device, mine is xiaomi ax 3200,but mtk does not have that limit with apple
Just to make sure I'm clear, you mean "no" the Apple devices don't have this AX problem with the stock firmware and driver? Sorry, it's been a long week.
apple does not have this problem with mtk drivers on openwrt. i do not use stock firmware.
Is this to be expected when running an iperf3 server on WDS client (192.168.1.2) and then running from the WDS AP (192.168.1.1):
root@OpenWrt:~# iperf3 -c 192.168.1.2 --bidir
Connecting to host 192.168.1.2, port 5201
[ 5] local 192.168.1.1 port 51050 connected to 192.168.1.2 port 5201
[ 7] local 192.168.1.1 port 51066 connected to 192.168.1.2 port 5201
[ ID][Role] Interval Transfer Bitrate Retr Cwnd
[ 5][TX-C] 0.00-1.00 sec 98.2 MBytes 821 Mbits/sec 0 1.94 MBytes
[ 7][RX-C] 0.00-1.00 sec 16.3 MBytes 136 Mbits/sec
[ 5][TX-C] 1.00-2.00 sec 90.9 MBytes 765 Mbits/sec 0 1.94 MBytes
[ 7][RX-C] 1.00-2.00 sec 15.5 MBytes 131 Mbits/sec
[ 5][TX-C] 2.00-3.00 sec 101 MBytes 847 Mbits/sec 0 1.94 MBytes
[ 7][RX-C] 2.00-3.00 sec 13.3 MBytes 112 Mbits/sec
[ 5][TX-C] 3.00-4.00 sec 106 MBytes 889 Mbits/sec 0 1.94 MBytes
[ 7][RX-C] 3.00-4.00 sec 11.7 MBytes 97.9 Mbits/sec
[ 5][TX-C] 4.00-5.00 sec 97.0 MBytes 813 Mbits/sec 0 1.94 MBytes
[ 7][RX-C] 4.00-5.00 sec 12.9 MBytes 108 Mbits/sec
[ 5][TX-C] 5.00-6.00 sec 91.0 MBytes 762 Mbits/sec 0 1.94 MBytes
[ 7][RX-C] 5.00-6.00 sec 14.0 MBytes 118 Mbits/sec
[ 5][TX-C] 6.00-7.00 sec 77.0 MBytes 648 Mbits/sec 0 1.94 MBytes
[ 7][RX-C] 6.00-7.00 sec 16.3 MBytes 137 Mbits/sec
[ 5][TX-C] 7.00-8.00 sec 106 MBytes 888 Mbits/sec 0 1.94 MBytes
[ 7][RX-C] 7.00-8.00 sec 13.1 MBytes 110 Mbits/sec
[ 5][TX-C] 8.00-9.00 sec 97.2 MBytes 818 Mbits/sec 0 1.94 MBytes
[ 7][RX-C] 8.00-9.00 sec 13.7 MBytes 115 Mbits/sec
[ 5][TX-C] 9.00-10.01 sec 95.9 MBytes 800 Mbits/sec 0 1.94 MBytes
[ 7][RX-C] 9.00-10.01 sec 12.5 MBytes 104 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID][Role] Interval Transfer Bitrate Retr
[ 5][TX-C] 0.00-10.01 sec 960 MBytes 805 Mbits/sec 0 sender
[ 5][TX-C] 0.00-10.01 sec 959 MBytes 803 Mbits/sec receiver
[ 7][RX-C] 0.00-10.01 sec 140 MBytes 118 Mbits/sec 296 sender
[ 7][RX-C] 0.00-10.01 sec 139 MBytes 117 Mbits/sec receiver
iperf Done.
That is 800Mbit/s from WDS AP to WDS client, but only 100Mbit/s from WDS client to WDS AP?
Also is it normal to see a lot of TCP retransmissions when uploading to WDS AP from WDS client?
root@OpenWrt:~# iperf3 -c 192.168.1.1
Connecting to host 192.168.1.1, port 5201
[ 5] local 192.168.1.2 port 48060 connected to 192.168.1.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 53.7 MBytes 449 Mbits/sec 147 171 KBytes
[ 5] 1.00-2.00 sec 47.8 MBytes 401 Mbits/sec 119 187 KBytes
[ 5] 2.00-3.00 sec 54.4 MBytes 456 Mbits/sec 130 124 KBytes
[ 5] 3.00-4.00 sec 50.5 MBytes 424 Mbits/sec 124 171 KBytes
[ 5] 4.00-5.00 sec 55.1 MBytes 461 Mbits/sec 118 129 KBytes
[ 5] 5.00-6.00 sec 54.4 MBytes 458 Mbits/sec 95 178 KBytes
[ 5] 6.00-7.00 sec 53.5 MBytes 449 Mbits/sec 160 164 KBytes
[ 5] 7.00-8.00 sec 48.5 MBytes 407 Mbits/sec 103 182 KBytes
[ 5] 8.00-9.00 sec 46.0 MBytes 386 Mbits/sec 127 194 KBytes
[ 5] 9.00-10.00 sec 48.8 MBytes 410 Mbits/sec 177 165 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 513 MBytes 430 Mbits/sec 1300 sender
[ 5] 0.00-10.00 sec 512 MBytes 429 Mbits/sec receiver
iperf Done.
@amteza does this correspond with your tests?
I just noticed this yesterday.. or at least the high retransmission rate when transmitting from a 4mac STA interface -> 4mac AP interface. If I switch to OpenWrt master or use the mac80211+hostapd packages from master on 22.03 I no longer see this behavior. So something likely in mac80211 between 22.03 and master seems to have fixed it.
What version are you running?
I haven't had a chance to narrow it down to a specific patch but if I had to guess maybe this is what fixes it: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=eb07020de2b4a5f89579f09f5060d4b9f070a356
2 Likes
Thanks a lot for your insight.
I'm running: OpenWrt 22.03-SNAPSHOT r19776-f579b8538b.
So maybe that patch needs to be backported to 22.03? BTW I'm only using WDS, no vlan?
I am testing on a 4mac interface only (no VLANs) right now as well.
I also just tested bringing back the patch mentioned in my last message and it does indeed solve the issue of high retransmissions.. definitely worth backporting to 22.03.
Summary of bidirectional iperf3 from 4mac STA <-> 4mac AP:
[ ID][Role] Interval Transfer Bitrate Retr
[ 5][TX-C] 0.00-10.00 sec 437 MBytes 367 Mbits/sec 0 sender
[ 5][TX-C] 0.00-10.00 sec 429 MBytes 359 Mbits/sec receiver
[ 7][RX-C] 0.00-10.00 sec 755 MBytes 633 Mbits/sec 0 sender
[ 7][RX-C] 0.00-10.00 sec 743 MBytes 623 Mbits/sec receiver
Downstream (RX) is still favored (which is probably ideal) but not nearly as bad as your first example.. and no retransmissions with the patch. If I just run upstream iperf3 from 4mac STA -> AP performance is also good and no retransmissions:
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 916 MBytes 769 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 908 MBytes 762 Mbits/sec receiver
1 Like
Excellent work in getting so quickly to the bottom of this @cmonroe!
@nbd please can you backport the above commit to solve this extreme asymmetry between download and upload in the context of WDS:
[ ID][Role] Interval Transfer Bitrate Retr
[ 5][TX-C] 0.00-10.01 sec 960 MBytes 805 Mbits/sec 0 sender
[ 5][TX-C] 0.00-10.01 sec 959 MBytes 803 Mbits/sec receiver
[ 7][RX-C] 0.00-10.01 sec 140 MBytes 118 Mbits/sec 296 sender
[ 7][RX-C] 0.00-10.01 sec 139 MBytes 117 Mbits/sec receiver
and whatever is causing the high number of retransmissions.