Setup
- Device: GL-BE9300 (Flint 3), firmware 4.10.1 (OpenWrt 23.05-SNAPSHOT r0-3601c2a49, kernel 5.4.213)
- ECM packages: kmod-qca-nss-ecm-premium / -wifi-plugin / kmod-qca-nss-sfe / kmod-qca-nss-ppe
5.4.213+gd34b66c-dirty - ECM config:
ecm.global.enabled=1,acceleration_engine='auto' - WAN: German cable ISP (DOCSIS, own cable modem in bridge mode), DS-Lite.
wan6is DHCPv6 withiface_dslite=1, which creates thewan6_4dslite interface (ds-wan6_4, MTU 1280, AFTR via DHCPv6 option 64). There is no native IPv4; IPv4 only runs through the DS-Lite tunnel.mtu_fix=1/ MSS clamping active. IPv6 LAN modenative(prefix delegation, no NAT66). - DPI, AdGuard Home, VPN, QoS and SQM are all off. No custom VLANs.
Symptom
On all LAN clients (iPhone, iPad, MacBook over Wi-Fi, and a wired Raspberry Pi), some web pages don't load or only load after several retries. When it happens, a single new IPv4 TCP connection hangs until the client gives up. IPv6 is not affected. Traffic generated by the router itself (curl on the Flint) is not affected.
Reproduction
Sequential HTTPS requests from a LAN client to about 23 popular sites (apple.com, google.com, amazon.de, spiegel.de, microsoft.com, …), 3 rounds, IPv4 forced, 10 s timeout:
for r in 1 2 3; do while read h; do
curl -4 -s -o /dev/null -m 10 -w "%{time_connect} $h\n" "https://$h/" || echo "FAIL $h"
done < sites.txt; done
| Condition | Mac (Wi-Fi 5 GHz) | Raspberry Pi (wired) | Router itself |
|---|---|---|---|
| ECM on (default) | 82/100, 61/69, 66/69 OK | 67/69 OK | 80/80 OK |
ECM stopped (/etc/init.d/qca-nss-ecm stop) |
69/69 | 69/69 | – |
ECM on, echo 1 > /sys/kernel/debug/ecm/front_end_ipv4_stop |
69/69, 69/69, 69/69 | 69/69 | – |
The same A/B/A result was also seen on an earlier date (11/100 vs. 100/100 OK, with TLS timeouts after a successful TCP handshake). Every failure is curl exit 28 (timeout). Several different CDNs are affected (Akamai, Fastly, CloudFront, Google).
Packet-level observation (nftables log on the Flint, prerouting -450 / postrouting 500)
For every failed connection:
- The client SYN arrives on
br-lan(logged once). - The SYN leaves via
ds-wan6_4. - The SYN-ACK arrives on
ds-wan6_4and is forwarded out ofbr-lanto the client. - The client sends no SYN retransmissions, so it received the SYN-ACK, but the connection never progresses (no TLS / no data delivered).
So the handshake completes through the slow path. The flow dies right after it is handed to the accelerated path. This looks like ECM/SFE/PPE mishandling IPv4-in-IPv6 (DS-Lite / ip6tnl) flows for some connections, possibly a wrong rule for the tunnel or the MSS/MTU (1280) handling in the offloaded path.
Workaround
Disable only the IPv4 front end. IPv6 stays accelerated:
echo 1 > /sys/kernel/debug/ecm/front_end_ipv4_stop
echo 1 > /sys/kernel/debug/ecm/ecm_db/defunct_all
This does not persist across reboots or ECM restarts, so it is re-applied via rc.local and cron. Throughput afterwards: IPv6 approx. 680 Mbit/s over Wi-Fi (accelerated). IPv4 approx. 350–500 Mbit/s over Wi-Fi (CPU forwarding, approx. 20–30 % softirq).
Related
- Flint 3 (GL-BE9300) Network Acceleration drops connection shows the same symptom class (website timeouts, retransmissions, fixed by disabling acceleration). In that thread it was PPPoE, and it went away after MTU changes (PPPoE MTU 1492 / WAN MTU 1508). The common factor may be a WAN MTU below 1500 (PPPoE 1492, DS-Lite 1280) that the accelerated path does not handle the way the slow path does (MSS clamping / fragmentation / ICMP frag-needed).
Request
- Please check ECM/NSS handling of DS-Lite (
dslite/ ip6tnl) IPv4 flows on the BE9300. - Please consider an option in the UI to disable acceleration for IPv4 only, or to exclude DS-Lite tunnels from acceleration automatically.
I'm happy to provide ecm_dump.sh / sfe_dump ipv4 / ppe_flow_dump output taken during a failure, or to test a beta firmware.
