S
S
Spotegg2021-09-19 16:12:20
VPN
Spotegg, 2021-09-19 16:12:20

How to route a VPN client to another VPN tunnel?

Hello!
There is Mikrotik 5.5.5.5, locale 192.168.31.0/24, it has a VPN server with a pool of addresses 192.168.31.230-240.
A PPTP tunnel (pptp-out1) was made from this Mikrotik to a VPN server on Windows Server 2016 (a pool of addresses 192.168.32.221-230 for VPN clients was made on Windows Server). Mikrotik's VPN server address on Windows Server 2016 is 192.168.32.221.
Mikrotik made a masquerading rule for the pptp-out1 interface.
A home computer is connected to Mikrotik via VPN l2tp, the address in the tunnel is 192.168.31.237

Mikrotik and devices that are connected to it directly via cable to ethernet ports ping 192.168.31.221
But a home computer connected to Mikrotik via vpn does not ping 192.168.31.221.
614737d4eb52b957650371.jpeg614737d8d9d10425718094.jpeg

Tell me how can this be fixed? Do you need to register a route on Mikrotik or at your home computer?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
S
Spotegg, 2021-09-20
@Spotegg

tracert 192.168.32.221 showed home router address on first hop:
Tracing route to 192.168.32.221 with max 30 hops
1 <1ms <1ms <1ms 192.168.22.1
2 * * * Request timed out.
3 * * * Query timed out.
I did route –p add 192.168.32.0 mask 255.255.255.255 192.168.31.231, but that didn't help.
If I check the box "Use the default gateway on the remote network" on my home computer (I send all home traffic through Mikrotik 5.5.5.5), then the tracing goes as it should:
Tracing the route to 192.168.32.221 with a maximum number of hops 30
1 11 ms 11 ms 11 ms 192.168.31.231
2 23 ms 22 ms 23 ms 192.168.32.221
But I don't need to drive all the traffic. Tell me how to solve this problem without the checkbox "Use the default gateway on the remote network"

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question