IP / Sec L2TP VPN client on Keenetic Extra: hosts on a remote network are pinged, but local ones from a remote network are not. How to fix?

Question

Network administration

Good afternoon friends.

I specifically screwed up. I have the following scheme:
There is Keenetic Extra with a 4G modem in the office, there is 1 computer (192.168.1.131) in the Keenetic local network (192.168.1.0). Keenetic created an outgoing (client) VPN connection via L2TP IP/Sec to a remote VPN server that has its own local network 192.168.2.0 and has an RDP server (192.168.2.9) on that network.

From the office, we quietly surf the Internet, as well as ping and connect to the RDP server in that remote VPN server network. True, I started pinging after I added 192.168.2.0 in the Keenetic routing rules with a subnet mask of 255.255.255.0 and a gateway of 192.168.2.10 (that is, this is the IP that Keenetic as a VPN client receives from DHCP on the VPN server). All is well on that side.

However, when I am in a session on the RDP server, opening the command line, trying to ping the office's local network, for example, the Keenetic address 192.168.2.10 or the computer on which I am sitting in the RDP session 192.168.

This is critical because a network printer is about to be turned on in the local office network, and therefore, without a ping from the RDP server, we will not see it from there and will not be able to print anything.

I tried to prescribe different route options on the VPN server, but I still didn’t understand how to do it correctly ...

Rough scheme of the above:


Can you tell me? The brain does not cook anymore.

Answer 1

The issue was resolved:
Everything was configured correctly, but I did not take into account that on Keenetic itself, when it receives an IP from 192.168.2.10, you need to open access at least by the ports trigger.