Hi everyone,
I have a WireGuard site-to-site setup and can’t get an RTSP camera stream through the tunnel, even though ICMP ping to the camera works fine. Hoping someone can point me at the right setting.
Setup:
• Self-hosted WireGuard server on a VPS (<VPS_IP>:51820)
• Remote site: GL.iNet router as WireGuard client (GL-X3000 over 4G, and a GL-MT2500/Brume 2 for comparison)
• Camera: Reolink RLC-823S2 (PoE, native RTSP/ONVIF) on the remote LAN, e.g. 192.168.30.21
• Server routes the remote subnet to the remote peer (AllowedIPs = 10.8.0.x/32, 192.168.30.0/24)
• ‘Allow Remote Access to LAN’ is ON on the remote GL.iNet router
What works:
• From the server/client I can ping the camera (192.168.30.21) through the tunnel, no packet loss
• With the Brume 2 connected via wired WAN the RTSP stream also works fine
What doesn’t:
• With the GL-X3000 over 4G, the RTSP stream on TCP 554 does not play (rtsp://user:pass@192.168.30.21:554/…). It either won’t open or connects and then shows no video. ICMP still works the whole time.
What I’ve already tried:
• Forcing RTSP over TCP instead of UDP
• Checked ‘Allow Remote Access to LAN’
• Verified the camera works locally on its own LAN
My questions:
- Is this a classic MTU / TCP-MSS-clamping issue on the WireGuard interface over 4G?
If so, what MTU do you recommend for a GL.iNet WG client on cellular, and how do I enable MSS clamping on current firmware?
-
Is there any firewall/zone forwarding setting beyond ‘Allow Remote Access to LAN’ needed to pass TCP 554 (vs. ICMP)?
-
Anything specific about the X3000 (cellular NAT) that would let ping through but drop larger TCP stream.
Did somebody have the Same Problem?
Thanks in advance for any pointers!
Pascal
