Hello, maybe someone can help me..
I try to find my failure since the last 3 days :-/

My client-network is 192.168.88.0/24, router-ip 192.168.88.250.
The l2tp-client is already working (client-ip 192.168.5.2).

i added srcnat, out-interface l2tp-out1 with "to-address" 192.168.5.2
and a routing-mark for one client (192.168.88.123).
FInally i added this route: Dst: 0.0.0.0/0, Gateway 192.168.5.1 (reachable via l2tp-out1) for this routing-mark.

If i do a tracert from 192.168.88.123 i.e. to 8.8.8.8 or google.de it is working and the gateway 192.168.5.1 is used - but it's not possible to open a website in browser..


Maybe someone could help me - whats wrong?

If i do a tracert from 192.168.88.123 i.e. to 8.8.8.8 or google.de it is working and the gateway 192.168.5.1 is used - but it's not possible to open a website in browser..

did you add routing for 192.168.5.0/24 to go out from l2tp-out1 ?
if your trace route is working then the routing should be fine. Sounds like an DNS issue.

you can enable log on the mangle rule and maybe using firewall filter to watch traffic going out l2tp-out1 interface, especially to port 53

Hello, thanks for your reply..
So this are my routes : My log was full with messages like this:

Message srcnat: in:(unknown 0) out:l2tp-out1, src-mac 2c:6f:c9:1c:73:09, proto UDP, 192.168.88.123:61069->8.8.8.8:53, len 75

>nslookup
DNS request timed out.
timeout was 2 seconds.
Standardserver: UnKnown
Address: 192.168.88.250

since update to RouterOS v6.42.7 its working - but extremly slow.. :-/

I'd suggest try to set 8.8.8.8 or 1.1.1.1 as DHCP server for your 192.168.88.0/24 clients, instead of 192.168.88.1. see if makes any difference.
you do this in IP - DHCP server - Network, I think.

thanks for reply!
The error is solved now (the problem with slow network-speed was caused by fasttracking) and i think the old ROS Version was faulty.