Page 1 of 1

Route needed with L2TP VPN

Posted: Wed Feb 08, 2017 11:42 am
by mgielissen
I've setup a L2TP VPN server. I can dial in but cannot ping the devices behind Mikrotik. In windows I need to add a route to get it working

Mikrotik LAN: 192.168.123.1
PPP Local Address: 192.168.222.1
VPN Pool: 192.168.222.100-192.168.222.120

To ping the devices on LAN I need to add this route on the client.
route add 192.168.123.0 mask 255.255.255.0 192.168.222.1

Can I add this route into a IPSEC policy or some kind?

Re: Route needed with L2TP VPN

Posted: Wed Feb 08, 2017 12:00 pm
by gustavomam

Re: Route needed with L2TP VPN

Posted: Wed Feb 08, 2017 1:20 pm
by mgielissen
Ok, but where can I add the route somewhere in the IPSEC policy? So when a client connects, this route must automatically added. I have more subnets behind Mikrotik, I can only reach them by adding the routes manually on the client after connecting.

Re: Route needed with L2TP VPN

Posted: Thu Feb 09, 2017 9:27 am
by gustavomam
Im not sure if you can do it that way with Ipsec policy with openvpn you can as well

Re: Route needed with L2TP VPN

Posted: Thu Mar 21, 2019 8:58 pm
by wombat
Hello,

Since 6.44+, the L2TP ipsec function has collapsed in a strange way

On the main router (L2TP server) range 10.xxx/24 several static routes - from the main router goes ping everywhere but from the client do not get to eg 10.x.1.254, eventually 10.x.16.1 I feel that the problem makes 1,254, the rest it works normally in those sub-systems. Do you have any idea where to look?