Fairly new to Teltonika and the RUTX50, i know the basics and i have set up a few p2p IPSec connections without issues
Now I have been following this guide, for trying to create a connection from some consultants PC directly to the modem so they can communicate with the local subnet
But when creating the IPSec part connection, as soon as that is created in the WEBGUI my L2TP connection changes to “down”
If i remove the IPsec connection that is bound to “transport” to my L2TP server config, it changes to up
If i try to connect to the IPsec tunnel as per the guide Windows PC settings, i can see an active client on the IPsec dashboard, but i suspect it drops after a few seconds becuase my L2TP shows as down.
Previously i have managed to connect to the L2TP without having any IPsec configuration, not sure how it works but is has worked before. Now there are no logs on my L2TP dashboard except when it starts “listening on port 1701” (this is with the IPsec config removed as stated above)
Do you have any ideas of what the issue is? why is L2TP automatically down when IPSec is configured?
1471 Sun Nov 9 22:31:20 2025 daemon.info xl2tpd[28561]: Listening on IP address 0.0.0.0, port 1701
1478 Sun Nov 9 22:47:14 2025 daemon.crit xl2tpd[28561]: death_handler: Fatal signal 15 received
This is the log from when i connect with my windows PC and IPSec is up (this says 1/1 connected bit L2TP is down still)
1679 Sun Nov 9 22:52:29 2025 daemon.info ipsec: 14[IKE] <l2tp_srv|12> CHILD_SA l2tp_srv_c{1} established with SPIs c247b139_i edd80150_o and TS xxx.xxx.xxx.xxx/32[udp/l2f] === xxx.xxx.xxx.xxx/32[udp/l2f]
With either scenario A or scenario B (tunnel is UP or tunnel is DOWN) do pings to the local network work either way? Or just with one of them, or not at all?
I’ll attempt to test this configuration out as soon as possible and will see if I’m able to replicate this issue.
I’ve tested this with a bit of an older firmware first - I went with 7.17.5 - I was experiencing the same exact issue as yours + I wasn’t able to connect from my PC at all.
I then went ahead and upgraded the firmware to the current latest firmware, which is 7.19 - instantly, both of the tunnel statuses were “Up” and my PC successfully connected to the tunnel:
Thank you! that worked perfectly, i did nothing but upgrade the firmware version and the tunnel is up and i can now ping from my assigned IP to the gateway that the teltonika has for my l2tp network
However i cant seem to for example ping the lan network on the device, just tried to reach the teltonika gateway for the LAN
Looking at the rules, it looks like it has automatically created a zone called “l2tp” and that has accept towards the “lan” and “wan” zone
Interesting, could you send me screenshots of your IPSec/L2TP configurations? Do you perhaps have Default route setting enabled? If so, could you try disabling it?
