Device: GL-BE3600 (Slate 7)
Summary: With Network Acceleration enabled, I saw two separate VPN-related problems that both went away once I disabled it. Posting in case this helps other users or the dev team.
Symptoms with Network Acceleration ON:
- WireGuard client profile connects successfully, but TCP traffic from devices behind the Slate stalls/hangs (e.g. speed tests get stuck at “Contacting server”).
-
- Tailscale repeatedly falls back to DERP instead of establishing a direct peer-to-peer connection.
- Workarounds I tried first that did NOT fix it:
-
- A firewall/nftables-style rule on the Slate intended to preserve Tailscale’s UDP source port (41641). After reboot/restart,
tailscale pingstill went viaDERP(sfo). -
- An OPNsense outbound NAT static-port rule for the Slate’s LAN IP (to stop source-port rewriting). Also did not change the DERP behavior.
tailscale netcheckstill showedMappingVariesByDestIP: true.
- An OPNsense outbound NAT static-port rule for the Slate’s LAN IP (to stop source-port rewriting). Also did not change the DERP behavior.
- What actually fixed it:
- Disabling Network Acceleration on the Slate. After that:
-
- WireGuard traffic stopped stalling immediately.
-
tailscale netcheckchanged toMappingVariesByDestIP: false.-
tailscale pingnow shows a directvia <public-ip>:<port>path instead ofvia DERP(…).-
- Throughput through the VPN path is now ~250 Mbps down / ~86 Mbps up.
- Why I’m posting: since a plain source-port/NAT fix didn’t resolve it, but toggling Network Acceleration did, it looks like the acceleration/offload path on the BE3600 may be interfering with both forwarded WireGuard client traffic and Tailscale’s NAT hole-punching. Would appreciate it if the team could take a look at whether Network Acceleration is compatible with WireGuard client mode + Tailscale, and whether this is expected behavior or a bug.
- Happy to provide firmware version, full
tailscale netcheckoutput, or logs if useful.
- A firewall/nftables-style rule on the Slate intended to preserve Tailscale’s UDP source port (41641). After reboot/restart,

