T
T
Talyan2021-05-06 00:05:23
Computer networks
Talyan, 2021-05-06 00:05:23

How to access Mikrotik over L2TP?

Hello. Something got confused in VPN routes. I ask for advice.

The scheme is as follows:
I connect to the office Mikrotik via L2TP.

I am given the address 172.16.1.250/32 gw 172.16.1.1
L2TP The address of the office microt is 172.16.1.1/24
Local: 192.168.1.0/24

A remote microtik is connected to the same office microt via L2TP:
L2TP IP: 172.16.1.2/32 gw 172.16. 1.1
Local: 192.168.2.0/24

In the settings of the office microt in the firewall, there is a rule:
FORWARD -s 172.16.1.0/24 -d 192.168.0.0/16 -j ACCEPT

From home with 172.16.1.250 I ping the office subnet 192.168.1.0/24
But, DAMN, I'm not pinging 192.168.2.0/24 from a remote microt.
Yes, figs with it with a remote LAN, I can’t even ping the L2TP address 172.16.1.2 from a remote microt.

Apparently, I forgot to register the route 172.16.1.0/24 via 172.16.1.1 on the remote Mikrotik.

At the same time, if I go to the office microt in the console, then I can ping both 172.16.1.2 and any computer from the remote subnet 192.168.2.0/24.

How can I connect to Mikrotik 172.16.1.2 while sitting at home, without going anywhere, having a route from the L2TP server to a remote office, but not having a route from home to a remote office?

What I have already tried to do:
Forward port 80 to the 80th port 192.168.2.1 on the office microte to the remote office to enter the webmord - it does not open.
Forwarded to 172.16.1.2 - also the same.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
T
Talyan, 2021-05-06
@flapflapjack

In general, I returned the old pool of ip addresses to L2TP clients, which routed without problems, and gained access to the remote Mikrotik.
The question can be considered closed and not relevant.

A
Alexander Karabanov, 2021-05-06
@karabanov

There is also RoMON (Wiki Manual:Tools/RoMON )

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question