Belkin RT3200/Linksys E8450 WiFi AX discussion

Cosmo · February 23, 2025, 5:40pm

Thank you. I'll certainly look into that.

immi803 · February 23, 2025, 11:18pm

@daniel I'm trying to Enable WED and response for cat /sys/kernel/debug/ppe0/bind is empty, though cat /sys/module/mt7915e/parameters/wed_enable
Y, further Hardware Flow Offloading is enabled as well as packet steering + steering flows (128), No sqm is installed, just ftp service is enabled ad block

Router has no nat behind or double nat , clean connection, bridgef modem behind to this router and e8450 doing pppoe
Any hint?

daniel · February 23, 2025, 11:59pm

The flow offloading unit which is also in charge of WED requires to actively track flows and push them into the offloading fast path. If all the router is doing is basically bridging wireless and Ethernet, ie. not actually routing, Linux doesn't track flows because there is no need to do so. In order to anyway enjoy the benefits of the offloaded fast path you need to install the bridger package which uses eBPF to achieve that.

Edit: I see you edited your message. Before you were saying that the modem acts as "PPPoE dialer", now you are stating that the E8450 is doing PPPoE. Please clarify, and maybe share /etc/config/network to avoid ambiguity.

immi803 · February 24, 2025, 12:15am

BusyBox v1.36.1 (2025-02-03 23:09:37 UTC) built-in shell (ash)

| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || || |
|___|| |||||_||| |____|
|| W I R E L E S S F R E E D O M

OpenWrt 24.10.0, r28427-6df0e3d02a

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

config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config globals 'globals'
option packet_steering '1'
option steering_flows '128'

config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'

config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '64'
option defaultroute '0'

config interface 'wan'
option device 'wan'
option proto 'pppoe'
option username 'xxx'
option password 'xxx'
option ipv6 '1'

config interface 'wan6'
option device '@wan'
option proto 'dhcpv6'
option reqaddress 'try'
option reqprefix 'auto'
option norelease '1'

root@OpenWrt:~#

immi803 · February 24, 2025, 12:32am

E8450 is doing pppoe
Apology for being ambiguous, further i shared network config in above post as well

root@OpenWrt:~# cat /sys/module/mt7915e/parameters/wed_enable
Y
root@OpenWrt:~#

root@OpenWrt:~# cat /sys/kernel/debug/ppe0/bind
root@OpenWrt:~#

daniel · February 24, 2025, 12:47am

cat /sys/kernel/debug/ppe0/entries

please.
Also note that WED (and records shown in bind) only kick in once there is a significant amount of single-stream traffic, eg. during a speed test or a large TCP download.

immi803 · February 24, 2025, 12:48am

root@OpenWrt:~# cat /sys/kernel/debug/ppe0/entries
0011e UNB IPv4 5T orig=8.219.70.8:8820->119.73.111.188:51120 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100003c0 ib2=00000000 packets=0 bytes=0
00e8a UNB IPv4 5T orig=192.168.1.50:44162->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500000bc ib2=00000000 packets=0 bytes=0
00fd4 UNB IPv4 5T orig=13.228.155.22:443->119.73.111.188:13296 new=36.7.170.128:44770->0.21.201.46:23126 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100000bc ib2=1a51c001 packets=0 bytes=0
015b2 UNB IPv4 5T orig=192.168.1.50:33054->192.168.1.1:53 new=36.7.170.128:44770->0.21.201.46:23126 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500000bd ib2=0000200a packets=0 bytes=0
01816 UNB IPv4 5T orig=38.90.96.96:5228->119.73.111.188:34042 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100003b9 ib2=00000000 packets=0 bytes=0
0192c UNB IPv4 5T orig=193.163.125.116:46510->119.73.111.188:49170 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100001b6 ib2=00000000 packets=0 bytes=0
01a4a UNB IPv4 5T orig=8.219.212.182:8820->119.73.111.188:48781 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100001b5 ib2=00000000 packets=0 bytes=0
01aaa UNB IPv4 5T orig=192.168.1.50:59026->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001be ib2=00000000 packets=0 bytes=0
01c4a UNB IPv4 5T orig=192.168.1.50:42466->192.168.1.1:53 new=36.7.170.128:0->0.21.201.46:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001b8 ib2=00000011 packets=0 bytes=0
01cfa UNB IPv4 5T orig=192.168.1.50:34234->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001b2 ib2=00000000 packets=0 bytes=0
01d34 UNB IPv4 5T orig=192.168.1.55:43497->8.219.70.8:8820 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100000af ib2=00000000 packets=0 bytes=0
01e52 UNB IPv4 5T orig=192.168.1.50:42222->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001b3 ib2=00000000 packets=0 bytes=0
01e8c UNB IPv4 5T orig=192.168.1.50:33921->192.168.1.1:53 new=36.7.170.128:43208->0.21.201.46:27608 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001bc ib2=0000200a packets=0 bytes=0
02032 UNB IPv4 5T orig=192.168.1.58:60059->8.219.212.182:8820 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100004bc ib2=00000000 packets=0 bytes=0
021be UNB IPv4 5T orig=8.219.70.8:8820->119.73.111.188:59328 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100000b1 ib2=00000000 packets=0 bytes=0
02254 UNB IPv4 5T orig=192.168.1.50:56045->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500000b2 ib2=00000000 packets=0 bytes=0
02434 UNB IPv4 5T orig=192.168.1.50:55773->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001bd ib2=00000000 packets=0 bytes=0
0270e UNB IPv4 5T orig=192.168.1.50:55360->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001bc ib2=00000000 packets=0 bytes=0
02a18 UNB IPv6 5T orig=2407:aa80:0003:0100:0000:0000:0000:0011:53->2407:aa80:0015:c92e:0000:0000:0000:0001:55455 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=5a0001b6 ib2=00000000 packets=0 bytes=0
02b50 UNB IPv4 5T orig=192.168.1.50:56943->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001b8 ib2=00000000 packets=0 bytes=0
02bd2 UNB IPv4 5T orig=8.219.70.8:8820->119.73.111.188:38615 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100001b7 ib2=00000000 packets=0 bytes=0
02d22 UNB IPv4 5T orig=192.168.1.50:56662->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500000b3 ib2=00000000 packets=0 bytes=0
03020 UNB IPv4 5T orig=192.168.1.50:54231->192.168.1.1:53 new=36.7.170.128:0->0.21.201.46:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500000b3 ib2=00000011 packets=0 bytes=0
030e8 UNB IPv4 5T orig=192.168.1.50:46003->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001b8 ib2=00000000 packets=0 bytes=0
0330e UNB IPv4 5T orig=192.168.1.59:51120->8.219.70.8:8820 new=36.7.170.128:0->0.21.201.46:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100003c0 ib2=00000010 packets=0 bytes=0
03424 UNB IPv4 5T orig=192.168.1.50:37333->192.168.1.1:53 new=36.7.170.128:0->0.21.201.46:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001b7 ib2=00000010 packets=0 bytes=0
035ba UNB IPv4 5T orig=192.168.1.50:45338->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001b8 ib2=00000000 packets=0 bytes=0
03646 UNB IPv4 5T orig=8.219.212.182:8820->119.73.111.188:60059 new=36.7.170.128:0->0.21.201.46:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100003bc ib2=00000011 packets=0 bytes=0
03662 UNB IPv4 5T orig=47.236.107.229:8820->119.73.111.188:37373 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100001bd ib2=00000000 packets=0 bytes=0
036a2 UNB IPv4 5T orig=192.168.1.50:53398->192.168.1.1:53 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500000b7 ib2=00000000 packets=0 bytes=0
0385c UNB IPv4 5T orig=192.168.1.57:34876->8.219.202.103:8820 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100001b8 ib2=00000000 packets=0 bytes=0
038e6 UNB IPv6 5T orig=2a03:b0c0:0003:00d0:0000:0000:168b:9001:443->2407:aa80:0015:c92e:aee2:5a56:78aa:34cc:50510 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=1a0001bd ib2=00000000 packets=0 bytes=0
03aae UNB IPv4 5T orig=192.168.1.50:46736->192.168.1.1:53 new=36.7.170.128:0->0.21.201.46:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001bd ib2=00000011 packets=0 bytes=0
03be8 UNB IPv4 5T orig=192.168.1.50:38451->192.168.1.1:53 new=36.7.170.128:0->0.21.201.46:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=500001be ib2=00000010 packets=0 bytes=0
03c5c UNB IPv4 5T orig=192.168.1.100:37373->47.236.107.229:8820 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100002bd ib2=00000000 packets=0 bytes=0
03df0 UNB IPv4 5T orig=116.100.160.210:60283->119.73.111.188:23 new=0.0.0.0:0->0.0.0.0:0 eth=00:00:00:00:00:00->00:00:00:00:00:00 etype=0000 vlan=0,0 ib1=100000b7 ib2=00000000 packets=0 bytes=0
root@OpenWrt:~#

quarky · February 24, 2025, 1:18am

How are you able to get into the Internet with default route disabled?

daniel · February 24, 2025, 2:05am

the actual NAT records look like garbage. so at least the debugfs code for PPE is broken on MT7622, maybe more... Also etype=0000 for all entries, which is wrong. They should be IPv4, IPv6 or PPPoE Session ethertypes.

immi803 · February 24, 2025, 2:30am

Any work around to make it work?

immi803 · February 24, 2025, 2:30am

This is correct settings in case of native ipv6

immi803 · February 24, 2025, 1:09pm

Can someone confirm if WED is working in latest snapshots?

el_charlie · February 24, 2025, 1:23pm

WED is working for me on my main RT3200 connected with DHCP to the GPON modem.

immi803 · February 24, 2025, 1:29pm

so you're connected with DHCP and using bridger to achieve this? right?
moreover are you using hardware offloading as well?

el_charlie · February 24, 2025, 1:37pm

No, I didn't install Bridger. Just WED, HW Offloading and packet steering.

My setup is the following:

Fiber modem ---> (LAN port, DCHP) RT3200 Main (LAN 1) ---> (WAN port as LAN) RT3200 Dumb AP.

Of course the second RT3200 that I use as dumb AP doesn't use WED because it doesn't do any routing.

immi803 · February 24, 2025, 1:43pm

i'll go clean with all settings (firstboot -y) and check again

waveguyd · February 24, 2025, 4:34pm

I found it! It is a PRC (mainland China) MIIT Network Access License (NAL) mark/label

The new NAL mark includes these elements: Logo, 4 Chinese Characters (either “进网许可” or “进网试用”), Model Number of the equipment, 21-digit Codes, Color in shading background (no shading background if in black and white).
https://typeapproval.com/miit-new-nal-mark/

Cosmo · February 25, 2025, 1:29am

Thank you for tracking that down. I had never seen those before. Not sure how someone in Roseville, California came by the two of them. I thought all of these models were made in Vietnam.

One of the kids who worked for me has Chinese roots, I'll send the pics over and see what he can find out. d

Lynx · February 26, 2025, 3:45pm

Actually results seem worse than I remember:

root@OpenWrt:~# iperf3 -c 192.168.1.1 -R
Connecting to host 192.168.1.1, port 5201
Reverse mode, remote host 192.168.1.1 is sending
[  5] local 192.168.1.3 port 45352 connected to 192.168.1.1 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  66.6 MBytes   558 Mbits/sec
[  5]   1.00-2.00   sec  70.0 MBytes   587 Mbits/sec
[  5]   2.00-3.00   sec  69.2 MBytes   581 Mbits/sec
[  5]   3.00-4.00   sec  66.8 MBytes   560 Mbits/sec
[  5]   4.00-5.00   sec  70.9 MBytes   595 Mbits/sec
[  5]   5.00-6.00   sec  69.6 MBytes   584 Mbits/sec
[  5]   6.00-7.00   sec  70.0 MBytes   587 Mbits/sec
[  5]   7.00-8.00   sec  69.6 MBytes   584 Mbits/sec
[  5]   8.00-9.00   sec  69.4 MBytes   582 Mbits/sec
[  5]   9.00-10.00  sec  71.0 MBytes   595 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.01  sec   696 MBytes   583 Mbits/sec    0             sender
[  5]   0.00-10.00  sec   693 MBytes   581 Mbits/sec                  receiver

Any way to check options relating to: he_bss_color, i.e. whether beamforming is active and which color has been set?

I take it that after setting:

 option local_pwr_constraint '0'

that restart of wpad / radio ought to be enough?

Otherwise not sure why the significant drop in bandwidth.

RMilk · February 28, 2025, 12:45am

It's not sufficient to use the installer. The issue is that it is like a temp boot partition. It will ALWAYS boot into recovery mode. You MUST re-flash with 24.10 UBI format (be sure the download is the UBI version) or you will lose all settings every time you reboot.
My experience with upgrading 2 of these E8450 from Woot. Amazing deal - $20 for a factory refurb. A few notes:

You MUST have internet access to complete the initial setup of the Linksys default firmware. I upgraded to the latest 1.2.* Linksys firmware, which required using the GitHub installer that was marked as "signed".
Install the signed firmware from Github. You should power off the machine each time you reboot.
Install the actual "UBI" version of 24.10 to install the permanent 24.10 OpenWRT version.

Belkin RT3200/Linksys E8450 WiFi AX discussion

| |.-----.-----.-----.| | | |.----.| |_ | - || _ | -| || | | || || | |_____|| |||||___||| |____| || W I R E L E S S F R E E D O M

OpenWrt 24.10.0, r28427-6df0e3d02a

| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || || |
|___|| |||||_||| |____|
|| W I R E L E S S F R E E D O M