Hyper-v 2008R2 subnet isolation between host and guest OS
Posted on 2011-02-26
I am going to show my networking ignorance to some degree here. I have a 2008R2 server running Hyper-v. This, obviously, in turn hosts a virtual environment. The host system has multiple network cards and on one nic communicates with a consumer linksys router. This router provides the host system with dchp, dns, and gives access to the internet. What I am wanting to do is to completely seperate the guest virtual environment from the physical (host's) while giving the virtualized guest environment internet access. Hyper-v uses a secondary nic in the host computer that the guest systems use. The virtual environment will host its own ad, dns and dhcp servers. For lab purposes, I do not want the physical system to communicate with the host system's dns or dhcp. I know this can be accomplished via subnetting, but I am a little limted without a vlan router. I would also like the host system to be able to access systems from in the virtual environment via direct routes, but I do not want the default subnet (let's say new laptops that join the wireless router's default subnet) to easily communicate with the virtual.
What additional hardware do I need to purchase? Is this even possible? I currently have 1 linkysys wrt54 wireless router and one cisco pix 501. My preference would be to use consumer level hardware, but if a single router with vlan capability will accomplish this, at a reasonable price, then I am open to that as well.
My linksys router is configured with a class C subnet. The router is configured as follows...
Subnet ID 0: Is the non virtual environment.
Subnet ID 1: Will be the virtual environment