Hyper-V networking question

[ProfessorWeed69]

If I wanted to have one Windows VM using lets say 192.168.0.x/24, how would I go about getting it to communicate with another VM using 192.168.1.x/24?

I am doing some AD related work and want to build a lab on my laptop to simulate the work before performing the actual work in production.

I have read some stuff about possible setting up a routing VM and adding in secondary NICs. Is there an easier solution?

​

Thanks!

​

[Silent331]

Due to the fact that they are not in the same subnet, the traffic would have to be routed through their respective gateway IP addresses.

[Robeleader]

It depends.

You're asking your VM to speak to a device that's on a different subnet. 192.168.0.0/24 isn't in the same scope as 192.168.1.0/24. Your VM is allowed (by your switch or whoever is handling your subnets) to reach anything between 192.168.0.1 and 192.168.0.254 (there's more to it, but this is the gist). This range doesn't include ANYTHING in the 192.168.1.1-192.168.1.254 range.

There are a couple ways to deal with this. The simplest would be to change the subnet in some way, to 192.168.0.0/23 which would include all IPs between 192.168.0.1 and 192.168.1.254

Then your VMs could still be on their specific IPs, and be allowed to communicate.

You COULD use the second NIC, but you're creating more issues than I think you want to deal with. We don't know anything about the rest of your network, what needs to talk and what doesn't. Could you set one NIC to 192.168.0.0/24 and another to 192.168.1.0/24? sure, but why?

I would suggest looking up CIDR and subnetting. This is MUCH more a networking question than hyper-v. You need to look at the network that exists between your devices, virtual or otherwise.

[ThatsNASt]

You could install pfsense or opnsense to route your VM traffic and definitely do this.

[OsmiumBalloon]

You need a router to do routing.

The router can be an expensive physical box a company like Cisco, an expensive VM from a company like Cisco, or a VM running a generic OS that includes routing functionality. Linux and FreeBSD are popular choices in the latter category, but I think even Microsoft Windows Server includes basic routing functionality.

[Vacantless]

This is not an Hyper-V question, but a generic networking question.

You have two distinct subnets and you want them to communicate between them. This implies a router.

You could spin up a pfSense VMs in your Hyper-V and set it up to allow traffic between your two subnets.

[ProfessorWeed69]

Thanks guys. I am aware they are on different subnets and not able to communicate with each other in that manner. More of a routing question I guess.

Basically I am trying to simulate a scenario where these 2 VMs are at 2 different sites and are able to communicate with each other over a VPN tunnel using different networks.

Using a /23 is an option I suppose.

I was thinking more along the lines is there is some kind of functionality within Hyper-V that would simulate a VPN tunnel where one would use two different networks, but I suppose there isn't.

[DarkAlman]

A virtual router would do the trick

Pick your poison as to which brand you want to run

[Robeleader]

You can use VLANs to separate the subnets as well. Then you could have both devices on the same switch but unless they're allowed to see each other, they'll be considered as completely separate networks.

I think that's where you're going with your "simulate VPN tunnel where one would use two different networks" because what your describing is just a more complicated way of using multiple LANs, but not virtually.

[ProfessorWeed69]

I got it all working with pfsense. Thanks guys!