Flint 3 (GL-BE9300) 4.10.1 – ECM IPv4 acceleration silently kills new TCP connections over DS-Lite (workaround: front_end_ipv4_stop)

Same router and firmware (GL-BE9300, 4.10.1), and the same symptom, but a different trigger and no DS-Lite. This may give you something that's easier to reproduce locally.

Trigger here: a custom VLAN on the LAN side. My WAN is plain DHCP IPv4 on the 2.5G WAN port (MTU 1500). Wi-Fi 7 / MLO is off.

Setup (made over SSH with uci, the same way as the Flint 3 IoT VLAN guide on this forum):

  • switch_vlan with vlan='10' and ports='3t 7t'.
  • eth1.10 bridged into br-iot.
  • Its own firewall zone, with iot -> wan forwarding and masquerade.
  • /etc/config/ecm stock (acceleration_engine 'auto').

Symptom: a wired client on VLAN 10 gets DHCP and DNS and can ping. A new IPv4 TCP connection to the internet completes the handshake, then stalls: TLS ClientHello and nothing back, 0-byte downloads, even plain HTTP. Wired clients on br-lan (eth1.1) are fine. Wi-Fi clients in the same br-iot are fine too.

Reproduction without any external switch: make LAN3 an untagged VLAN 10 port:

swconfig dev switch1 vlan 1 set ports "3t 4 6 7"
swconfig dev switch1 vlan 10 set ports "3t 5 7t"
swconfig dev switch1 port 5 set pvid 10
swconfig dev switch1 set apply

Then plug a laptop into LAN3 and run curl ``https://1.1.1.1/.

A/B tests (same client; curl https://1.1.1.1/ plus a 50 MB HTTPS download):

acceleration_engine / setting Managed switch port, VLAN 10 tagged on LAN1 LAN3 untagged VLAN 10
auto stalls stalls
ppe-sfe stalls not tried
auto + /proc/sys/ppe/bridge_mgr/fdb_disabled=1 stalls not tried
auto + vlan_as_vp_interface=eth1 (eth1.10 recreated afterwards) not tried stalls
auto + front_end_ipv4_stop=1 + defunct_all works not tried
sfe works works

Routed traffic from br-lan to a host on VLAN 10 (no NAT) works under auto. Only NAT to WAN breaks.

ecm_dump.sh for a stuck flow:

conns.conn.13441.from_interfaces.0.ethernet.iface.name=eth1
conns.conn.13441.from_interfaces.1.vlan.iface.name=eth1.10
conns.conn.13441.from_interfaces.1.vlan.tag=a
conns.conn.13441.from_interfaces.2.bridge.iface.name=br-iot
conns.conn.13441.to_interfaces.0.ethernet.iface.name=eth0
conns.conn.13441.ppe_v4.ported.can_accel=1

Taken with this thread and the Slate 7 WireGuard report that staff reproduced on 4.10.0 ([4.10.0] Slate 7 (GL-BE3600): WireGuard client passes no LAN TCP traffic while Network Acceleration (ECM) is on – worked on 4.9.2), it looks like 4.10.x PPE mishandles IPv4 NAT flows whenever the path includes something beyond a plain port: a tunnel, a VPN or a VLAN.

Workaround that keeps most of the speed: uci set ecm.global.acceleration_engine='sfe'; uci commit ecm, then restart qca-nss-ecm. That gives about 870/360 Mbps over Wi-Fi here, versus 886/416 under auto. It persists across reboots, unlike front_end_ipv4_stop. @inquisitive, it may be worth trying on DS-Lite too.

Happy to run ppe_flow_dump / sfe_dump ipv4 while reproducing, or to test a beta.