I want to create a clone of our production servers to test upgrades etc, but I need some help figuring out how to provide network access to the isolated network.
I have a dedicated Hyper-v host where I am going to restore a full copy of the servers and connect the VM’s to a “Private Network”.
The servers need to retain their IP’s from the production network (10.47.2.0/24).
I have created a vyos VM with 2 nics, eth0 is connected to the Private Network with an interface address of 10.47.2.1 to simulate the production gateway.
I want to be able to remote desktop to the cloned virtual servers through the eth1 nic in the VYOS VM using a masqurade IP.
Client wants to connect to cloned server with real ip of 10.47.2.10 using a masqurade ip of 126.96.36.199.
On the client will be added a static route to the IP of VYOS eth1. ROUTE ADD 188.8.131.52 MASK 255.255.255.0 IP_ADDRESS_OF_VYOS_ETH1
Client [10.47.20.105] —> Eth1_VYOS —> VYOS_Eth0 [10.47.2.1] —> Server1 [10.47.2.10]
The cloned servers in the isolated network are not allowed to initiate traffic out from the isolated network to avoid conflicts with production servers.
Basically I want to use the same functionality as Veeam Virtual Lab described here, but this virtual lab is not permanent meaning changes are destroyed once the lab is shut down.