We are facing an issue with L2TP VPN on Teltonika RUT241 devices running firmware version 07.19.4.
Observed behavior:
When L2TP VPN is enabled, the device loses internet connectivity
When L2TP VPN is disabled, the internet connection is immediately restored
Additional information:
The same L2TP configuration works correctly on a RUT200 with the same firmware version (07.19.4)
The issue seems to affect specifically the RUT241 model
At this stage, no configuration differences have been identified that could explain the behavior.
Has anyone experienced a similar issue with L2TP on RUT241? Is there any known limitation, fix, or recommended troubleshooting (logs, settings, patches) for this case?
Thanks for the detailed report. The symptom - internet drops when L2TP is enabled, restores when disabled, works fine on RUT200 - points to a routing conflict where the L2TP tunnel is overriding the RUT241’s default WAN route.
Please work through the following steps:
Check the “Default Route” option
Go to Services → VPN → L2TP → [your instance] → Edit and confirm whether “Default route” is enabled. This should only be on if you’re routing all internet traffic through the VPN server as a proxy. If enabled unintentionally, it replaces the WAN gateway with the tunnel - which matches your symptoms exactly.
Inspect the routing table while L2TP is active
SSH into the RUT241 and run: ip route
You should still see a valid default route via your WAN interface. If it’s missing or pointing to the tunnel (e.g. ppp0), that’s your culprit.
Check logs at VPN connect time
Run: logread | grep -i l2tp and logread | grep -i route
Look for any route additions or deletions that coincide with the tunnel coming up.
Compare routing tables with the RUT200
With L2TP active on both devices, check Status → Routes in the WebUI and compare side-by-side. Any difference will help isolate whether this is a platform-specific behaviour.
Test with a clean config
If the device was upgraded with “Keep Settings”, try a factory reset and reconfigure from scratch to rule out config mismatches.
Update to the latest firmware
Try updating your firmware to the latest release - several routing-related fixes have been included in recent builds.