Configure virtualization home lab

[jmike72]

Hi all.

I have a home Hyper-V lab where the VM’s are running on an internal network, so they don’t have any external access. To add the external access, I’ve added a virtual router using VyOS.

On my actual config, I have the following IP’s/Configuration:

Router
WAN connection
Internal IP: 192.168.1.1
DHCP server running here

Management PC
External IP: 192.168.1.102

Hyper-V
External IP: 192.168.1.100
Internal IP: 192.168.10.2
DHCP server for the internal IP

Virtual Router
External IP: 192.168.1.101
Internal IP: 192.168.10.1
NAT running

VM’s
Internal IP: 192.168.10.0/24

My idea with this configuration was to allow the management PC to RDP to any of the VM’s running on my Hyper-V and for that I’ve added a static route for the 192.168.10.0/24 network that points to the 192.168.1.101 IP of the virtual router, but that doesn’t work as I have the default route 192.168.1.0/24 pointing to 192.168.1.1 on the physical router.

I was thinking about creating a virtual IP on my management PC on the 192.168.20.0/24 network and add a third NIC to the virtual router on that same network and add then add the static route for the 192.168.10.0/24 network to the 192.168.20.x IP on the virtual router.

Will that work, or do you have a better idea?

Thanks,
Mike

 

[kevnich2]

From your management computer, can you ping and access the virtual router's interface of 192.168.10.1 ? You also need to add a firewall rule in the virtual router that will allow traffic from 192.168.1.x to get to your 192.168.10.x subnet as well

 

[jmike72]

From your management computer, can you ping and access the virtual router's interface of 192.168.10.1 ? You also need to add a firewall rule in the virtual router that will allow traffic from 192.168.1.x to get to your 192.168.10.x subnet as well

No, from the management PC I can't ping the 192.168.10.1. As for the firewall, I have a rule to allow all the traffic.

Mike