L2TP / IPSec client. Problem with routes?

Question

Mikrotik

Good day!

The essence of the problem is simple, on Mikrotik RBD52G-5HacD2HnD-TC (bought on vacation) a connection to the L2TP IPSec server and route 192.168..0/24 (Gateway, respectively, to the connection interface) are configured. From the router itself, pings go to the working machine, but not from the local machine. But if you connect from the local machine, then everything works.
RouterOS version LTS v6.45.9.
Tried disabling firewall rules, didn't help. Tried with different OS and laptop (via WiFi) nothing changes.

And the joke is that on vacation everything worked, as I came home, such a mess.

PS If you need something from the configs, I'll throw it separately, I just started tinkering with Mikrotik.

ANSWER: L2TP / IPSec client. Problem with routes?
Write something like this:

/ip firewall nat add chain=srcnat action=masquerade out-interface=<interface list>

Answer 1

Since everything works when connected directly, but not through a router, then the endpoint has no idea about your network and cannot return the ping accordingly - it does not know where to send the packet.
Subnet addresses are not registered in Mikrotik, or on the computer itself.
When connecting L2TP, addresses are allocated - try to ping them first, both dedicated and server.