I cannot reproduce your issue. My laptop is currently connected to a LAN port of an RT-BE92U, and I can get my full fibre Gbps when running a speedtest (940/940).
Hello RMerlin,
Thank you for looking into it. Now that I have all the facts, I can resolve the issue. Either disable the DNS Director or add the client to the NO Redirections Rule.
TLDR;
To deep-dive into what's going on, I monitored the process and observed that bcmsw_rx (Broadcom Switch Receiver) consumed the max CPU while running speedtest (on my Google Nest Router, and on the RT-BE92U router).
In version 3006.102.5_0, the introduction of new SDN (Software Defined Networking) and VLAN isolation code has created a conflict that "breaks" the hardware shortcut, forcing the bcmsw_rx process to manually handle the traffic.
Release note:
The release notes for
3006.102.5_0 highlight a specific fix:
"Fixed: OpenVPN server set to 'Internet only' would fail to block LAN access (invalid firewall rule from SDN was bypassing it)."
bcmsw_rx is the driver process that receives those "orphaned" packets from the switch. When it hits 100% or high usage, it acts as a
bottleneck, capping your speed (often exactly to the 150–300 Mbps range you are seeing).
"FIXED: DNSDirector 'Router' mode would not always work properly with IPv6 (now uses
REDIRECT instead of DNAT... this was also necessary for improved Guest Network support)."
Code:
RT-BE92U-3F50:/tmp/home/root# iptables -nvL | grep
-i SDN
448 88303 SDN_FI all -- * * 0.0.0.0/0 0.0.0.0/0
135K 150M IPSECSSDN all -- * * 0.0.0.0/0 0.0.0.0/0
982 207K SDN_FF all -- * * 0.0.0.0/0 0.0.0.0/0
Chain IPSECSSDN (1 references)
Chain SDN_FF (1 references)
0 0 SDN_IA all -- * * 0.0.0.0/0 0.0.0.0/0
Chain SDN_FI (1 references)
Chain SDN_IA (1 references)
So when I disabled DNS Director, it worked as expected. Then I enabled speed cap again to 150 Mbps. 2nd time, I have added a specific rule to
and its works fine.