Belkin RT3200/Linksys E8450 WiFi AX discussion

using the latest SNAPSHOT - r20877-7d6032f310

[ ID][Role] Interval           Transfer     Bitrate         Retr
[  5][TX-C]   0.00-300.00 sec  21.2 GBytes   608 Mbits/sec    5             sender
[  5][TX-C]   0.00-300.03 sec  21.2 GBytes   608 Mbits/sec                  receiver
[  7][RX-C]   0.00-300.00 sec  19.6 GBytes   560 Mbits/sec  4522             sender
[  7][RX-C]   0.00-300.03 sec  19.6 GBytes   560 Mbits/sec                  receiver

one direction to remote server:
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-300.00 sec  30.3 GBytes   867 Mbits/sec  470             sender
[  5]   0.00-300.02 sec  30.3 GBytes   867 Mbits/sec                  receiver

one way to server on device:
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-300.00 sec  35.2 GBytes  1.01 Gbits/sec    0             sender
[  5]   0.00-300.01 sec  35.2 GBytes  1.01 Gbits/sec                  receiver

bidir to server on device:
[ ID][Role] Interval           Transfer     Bitrate         Retr
[  5][TX-C]   0.00-300.00 sec  26.6 GBytes   762 Mbits/sec    1             sender
[  5][TX-C]   0.00-300.02 sec  26.6 GBytes   762 Mbits/sec                  receiver
[  7][RX-C]   0.00-300.00 sec  11.8 GBytes   339 Mbits/sec    7             sender
[  7][RX-C]   0.00-300.02 sec  11.8 GBytes   339 Mbits/sec                  receiver

yes iperf on the device does max the cpu out.
I'm using iperf on a separate machine not on the device. seems rater blalnaced to me. when I hosted iperf on the device it was rather unbalanced.

but yeah retransmits a little high. could just be how it is though with everything on wifi.

The anemic switch is the devices weakest point. if only it had a 2.5gb external port or a 10g port but those are just to expensive still. sigh

No, mate, it does not. Look, the following test is from client WDS to AP WDS:

root@nanohd-downstairs:~# iperf3 -c nanohd-upstairs.lan --bidir
Connecting to host nanohd-upstairs.lan, port 5201
[  5] local 2403:5804:6e::2 port 47878 connected to 2403:5804:6e::3 port 5201
[  7] local 2403:5804:6e::2 port 47890 connected to 2403:5804:6e::3 port 5201
[ ID][Role] Interval           Transfer     Bitrate         Retr  Cwnd
[  5][TX-C]   0.00-1.00   sec  12.0 MBytes   101 Mbits/sec    0    484 KBytes
[  7][RX-C]   0.00-1.00   sec  22.4 MBytes   188 Mbits/sec
[  5][TX-C]   1.00-2.00   sec  22.2 MBytes   186 Mbits/sec    0    484 KBytes
[  7][RX-C]   1.00-2.00   sec  19.9 MBytes   166 Mbits/sec
[  5][TX-C]   2.00-3.00   sec  15.5 MBytes   131 Mbits/sec    1    484 KBytes
[  7][RX-C]   2.00-3.00   sec  15.3 MBytes   129 Mbits/sec
[  5][TX-C]   3.00-4.00   sec  15.6 MBytes   131 Mbits/sec    0    484 KBytes
[  7][RX-C]   3.00-4.00   sec  15.6 MBytes   131 Mbits/sec
[  5][TX-C]   4.00-5.00   sec  22.0 MBytes   185 Mbits/sec    0    484 KBytes
[  7][RX-C]   4.00-5.00   sec  21.7 MBytes   182 Mbits/sec
[  5][TX-C]   5.00-6.00   sec  26.8 MBytes   225 Mbits/sec    0    484 KBytes
[  7][RX-C]   5.00-6.00   sec  5.85 MBytes  49.1 Mbits/sec
[  5][TX-C]   6.00-7.00   sec  24.1 MBytes   202 Mbits/sec    0    484 KBytes
[  7][RX-C]   6.00-7.00   sec  19.9 MBytes   167 Mbits/sec
[  5][TX-C]   7.00-8.00   sec  21.3 MBytes   179 Mbits/sec    0    484 KBytes
[  7][RX-C]   7.00-8.00   sec  22.6 MBytes   190 Mbits/sec
[  5][TX-C]   8.00-9.01   sec  19.1 MBytes   159 Mbits/sec    1    484 KBytes
[  7][RX-C]   8.00-9.01   sec  21.1 MBytes   176 Mbits/sec
[  5][TX-C]   9.01-10.00  sec  15.9 MBytes   134 Mbits/sec    0    484 KBytes
[  7][RX-C]   9.01-10.00  sec  17.7 MBytes   149 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID][Role] Interval           Transfer     Bitrate         Retr
[  5][TX-C]   0.00-10.00  sec   195 MBytes   163 Mbits/sec    2             sender
[  5][TX-C]   0.00-10.01  sec   194 MBytes   162 Mbits/sec                  receiver
[  7][RX-C]   0.00-10.00  sec   183 MBytes   153 Mbits/sec  767             sender
[  7][RX-C]   0.00-10.01  sec   182 MBytes   152 Mbits/sec                  receiver

iperf Done.

The network is busy with a Youtube stream and a Facetime call, and WDS connection is only 620-780 Mbps (WiFi 5). So it looks much more balanced than yours; however, I can see a significant number of retransmissions, not as many as you.

And regarding uploading to WDS AP from the WDS client, I don't see the number of retransmissions you see at all; see below:

root@nanohd-upstairs:~# iperf3 -c nanohd-downstairs.lan
Connecting to host nanohd-downstairs.lan, port 5201
[  5] local 2403:5804:6e::3 port 55454 connected to 2403:5804:6e::2 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.01   sec  40.9 MBytes   340 Mbits/sec    0    478 KBytes
[  5]   1.01-2.02   sec  40.1 MBytes   334 Mbits/sec    0    478 KBytes
[  5]   2.02-3.03   sec  40.4 MBytes   336 Mbits/sec    0    478 KBytes
[  5]   3.03-4.03   sec  42.4 MBytes   355 Mbits/sec    0    478 KBytes
[  5]   4.03-5.02   sec  24.5 MBytes   207 Mbits/sec    1    478 KBytes
[  5]   5.02-6.01   sec  39.9 MBytes   336 Mbits/sec    0    478 KBytes
[  5]   6.01-7.00   sec  40.6 MBytes   345 Mbits/sec    0    478 KBytes
[  5]   7.00-8.00   sec  38.5 MBytes   323 Mbits/sec    0    478 KBytes
[  5]   8.00-9.01   sec  40.6 MBytes   339 Mbits/sec    0    478 KBytes
[  5]   9.01-10.00  sec  21.5 MBytes   181 Mbits/sec    2    505 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   369 MBytes   310 Mbits/sec    3             sender
[  5]   0.00-10.00  sec   369 MBytes   309 Mbits/sec                  receiver

iperf Done.

Note this test added a Netflix stream to the test. My wifey just told me to f-off and to stop playing with the network. :smiley:

I'm running in WDS AP version OpenWrt SNAPSHOT, r20876-f38276c9be and in WDS client version OpenWrt SNAPSHOT, r20885-629f2de1a7.

@Lynx, I just noted I've got the patch https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=eb07020de2b4a5f89579f09f5060d4b9f070a356 in both devices.

3 Likes

Right! Further confirmation we need this in 22.03.

a packet capture via tcpdump of your misbehaving test would be interesting. tcpdump -i the_interface -s 128 -w somewherewithstorage.cap

Anyone else having reboot issues? I have two set to reboot once a week. About after three weeks it reboots and doesn’t come back up until I manually go unplug the router and plug it back in. I have v0.6.5 with 22.03 installed.

I asked in the AdGuard Home thread if I need to worry about running out of storage space when installing with opkg on Linksys E8450 / Belkin RT3200, since the wiki mentions a 100MB free disk/flash space requirement. Didn't yet get a clear answer.

But now I'm wondering: the version of AdguardHome in the repository is 0.107.6-1 (this release is 6 months old). I'm on the latest firmware version 22.03.0 - r19685-512e76967f. In the OpenWrt master branch there's version v0.107.12 (committed by @hnyman, now 1 month behind). Latest release is v0.107.16.

What is the reason this package is not fully up to date? I think installing through opkg would be most convenient (also seems to be require less storage space). But I would also like to be fairly up to date.

I believe the package feeds are versioned. Not sure why a latest snapshot would not return a more recent version. I see:

# opkg list | grep adguard
adguardhome - 0.107.12-1 - Free and open source, powerful network-wide ads and trackers blocking DNS server.

Openwrt is a community project. You are welcome to update and create a PR.

EDIT: https://github.com/openwrt/packages/pull/19585

2 Likes

Cool, you made a PR! :slight_smile:

But when would this newer version become available on 22.03.0?

For example when I check Updates in the OpenWrt Software page on my router I see 7 package updates. For example: luci-app-opkg git-22.154.41881-28e92e3 » git-22.273.29004-9f6876b.

I'd love to see the newer version of AdGuard listed there too.

Or can we only have new versions of packages when a new OpenWrt version is released? (and the reason we don't have v0.107.11 and v0.107.12 is because they were committed after the 22.03.0 was made?)

Yes, unless the update is backported. Alternatively, you can use a nightly snapshot.

So @nbd will this be ported to 22.03 given that it apparently significantly improves upload performance in at least WDS context?

Thanks, good to know. In that case I'd rather run AdGuard on my home server (with Docker).

1 Like

Just noticed that OpenWrt 22.03.1 is (technically) out, but are the recent updates are or we have to wait for next major release?

Cheers.

should be.

@daniel - I wanted to follow-up on the instability I noticed when booting with
options mt7915e wed_enable=Y in my /etc/modules.conf. Initially, I thought the broken WiFi was due to bridger being enabled, but I disabled bridger and found that I got a similar broken WiFi.

  • Only one of my 3 SSIDs was visible
  • Devices could not connect to it

I found this in dmesg:

[ 3093.719338] mt7915e 0000:01:00.0: Message 00005aed (seq 4) timeout
[ 3114.108265] mt7915e 0000:01:00.0: Message 000026ed (seq 5) timeout
[ 3134.588086] mt7915e 0000:01:00.0: Message 000025ed (seq 6) timeout
[ 3134.594315] wlan1-1: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)
[ 3155.067961] mt7915e 0000:01:00.0: Message 000026ed (seq 7) timeout
[ 3175.547821] mt7915e 0000:01:00.0: Message 000025ed (seq 8) timeout
[ 3175.554154] ------------[ cut here ]------------
[ 3175.558774] WARNING: CPU: 0 PID: 3916 at ___ieee80211_stop_tx_ba_session+0x36c/0x3d0 [mac80211]
[ 3175.567580] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mt7915e mt7615e mt7615_common mt76_connac_lib mt76 mac80211 cfg80211 slhc nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c hwmon crc_ccitt compat cls_flower act_vlan cls_bpf act_bpf sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_tcindex cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred act_gact seqiv usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk_hcd xhci_hcd gpio_button_hotplug usbcore usb_common
[ 3175.645851] CPU: 0 PID: 3916 Comm: kworker/u4:0 Tainted: G S                5.15.73 #0
[ 3175.653778] Hardware name: Linksys E8450 (UBI) (DT)
[ 3175.658657] Workqueue: phy1 ieee80211_ba_session_work [mac80211]
[ 3175.664743] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 3175.671714] pc : ___ieee80211_stop_tx_ba_session+0x36c/0x3d0 [mac80211]
[ 3175.678399] lr : ___ieee80211_stop_tx_ba_session+0x218/0x3d0 [mac80211]
[ 3175.685084] sp : ffffffc00ab5bca0
[ 3175.688396] x29: ffffffc00ab5bca0 x28: ffffffc008b8d810 x27: ffffff8004cd1000
[ 3175.695528] x26: 0000000000000000 x25: ffffffc008b8d000 x24: ffffff80024c1080
[ 3175.702659] x23: ffffff800256a0e8 x22: ffffffc000a164ec x21: 0000000000000001
[ 3175.709790] x20: ffffff8000800500 x19: ffffff8004cd1000 x18: 000000000000018e
[ 3175.716921] x17: 0000000000000000 x16: 0000000000000002 x15: 0000365dce5b1d78
[ 3175.724052] x14: 00003631c19ea3e0 x13: ffffffc008818680 x12: 00000000f5257d14
[ 3175.731183] x11: 00000000f5257d14 x10: 000000000000b67e x9 : 0000000000000001
[ 3175.738314] x8 : 00000000005b4dc0 x7 : 0000000000000001 x6 : ffffff801fea8140
[ 3175.745444] x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffffff8000d22c00
[ 3175.752573] x2 : 0000000000000000 x1 : ffffff8000d22c00 x0 : 00000000ffffff92
[ 3175.759705] Call trace:
[ 3175.762142]  ___ieee80211_stop_tx_ba_session+0x36c/0x3d0 [mac80211]
[ 3175.768423]  ieee80211_ba_session_work+0x36c/0x390 [mac80211]
[ 3175.774182]  process_one_work+0x200/0x3b4
[ 3175.778189]  worker_thread+0x17c/0x4dc
[ 3175.781931]  kthread+0x11c/0x130
[ 3175.785153]  ret_from_fork+0x10/0x20
[ 3175.788722] ---[ end trace 7a34be0feb127501 ]---
[ 3196.027701] mt7915e 0000:01:00.0: Message 000026ed (seq 9) timeout
[ 3216.507557] mt7915e 0000:01:00.0: Message 000025ed (seq 10) timeout
[ 3216.513896] wlan1-1: HW problem - can not stop rx aggregation for xx:xx:xx:xx:xx:xx tid 0
[ 3236.987433] mt7915e 0000:01:00.0: Message 00005aed (seq 11) timeout
[ 3257.467301] mt7915e 0000:01:00.0: Message 000025ed (seq 12) timeout
[ 3277.947176] mt7915e 0000:01:00.0: Message 0000aded (seq 13) timeout
[ 3298.427053] mt7915e 0000:01:00.0: Message 00005aed (seq 14) timeout
[ 3318.906938] mt7915e 0000:01:00.0: Message 00005aed (seq 15) timeout
[ 3339.386809] mt7915e 0000:01:00.0: Message 00005aed (seq 1) timeout
[ 3359.866694] mt7915e 0000:01:00.0: Message 000026ed (seq 2) timeout

I have since removed the tweak to enable WED in the module. If you or others are thinking about enabling WED by default, I do not recommend it right now at last.

1 Like

Are software or hardware flow offloading enabled in your firewall config?

Neither are enabled. This device is a dumb access point/no firewall.

Did this configuration ever work with earlier builds?

Yes, configuration works perfectly. Only ran into issues when I began to play with WED and with bridger.

Question. It seems MTU of MT7622 is limited to about 2026 bytes.

Do this also applies to the switch ports ?

I have two servers on my LAN that have MTU9000 and were working with older Archer C7 but now they don't after switching to a RT3200 and confirmed using ping -s <size>

Does the 22.03.0 image uses DSA for the switch ports ?

TIA

as far as I'm aware it is DSA capable. I'm looking at the switch data sheet page 429 is rx jumbo size.

cpu and switch both state:
 Support packet length up to 15K for jumbo frames application