1:1 nat thru VPN

I am trying to do something, which conceptually looks extremely easy. I want to create a “machine proxy” for a server I have at home in a different location.

Excuse my very poor schema below
shema.jpg
Basically I have a home network which is connected to the internet thru a mikrotik system (RB1100AH) which has multiple wan interfaces and public ips.
In a remote location where unfortunately I have to leave the internet provider box as the main gateway, I want to setup a second mikrotik box (in the lan) which could act as a “proxy” forwarding all traffic received to a machine located in my home lan (called the home server above). Ideally machine located in the remote lan and connecting to any service on the mikrotik would connect transparently to the home server.

I tried many different config, using as well different vpn type (I need basic encryption but nothing really confidential would flow) but I could not reach any success to date. Is anyone here already tried to achieve something similar ?

If this is too complex is there at least a simple option to forward specific port in an easy manner (like one could do in 5s using an ssh connection ?)

Thanks !

What exactly is the problem?

Create some VPN server on RB1100AH, any kind you like. Connect to it from future proxy device and set up proper routing, so that you’ll be able to access 192.168.2.10 from 192.168.1.x (test it from 192.168.1.10). Then choose some of the following:

a) If you can, configure Machine 1 with static route to 192.168.2.10 via 192.168.1.10 and you’re done.
b) If Machine 1 is something special and it can’t have static routes and it doesn’t need internet access, set its default gw to 192.168.1.10.
c) If connecting to some local address is the only option (for whatever reason), configure proxy to dstnat anything to 192.168.1.10 to 192.168.2.10. It will be enough for connections initiated from 192.168.1.11. If you want it to work also in other direction (connections from 192.168.2.10 to 192.168.1.11), add srcnat rule to change source of packets from 192.168.2.10 to 192.168.1.10.