• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Routing between virtual networks/subnets

  • Thread starter Deleted member 12106
  • Start date
D

Deleted member 12106

Guest
Greetings. I am in the process of setting up a stand alone lab network for educational purposes. I am running server 2012r2 w/ hyper-v.

Right now my layout looks like this:
192.168.1.1/24
192.168.10.1/24

I would like to setup a domain controller on 192.168.10.1/24, and still have access to the other network. Last night I installed a domain controller and gave it 2 nics. I can access the other subnet shares, but no internet. Doing some google-foo, it is a bad practices to have 2 nics in a DC. It is suggested to use a router. This is about as far as I got on it last night.

Surely I am not the only one to encounter this, so perhaps someone has an easy solution.
 
Just use NAT mode, and break out that second segment as a pure L2 segment. Unless you need to route between them within the P_Host ?

e.g. Let your 192.168.1.0/24 subnet be the egress for Internet, and run that VLAN in NAT mode.

Then take your 192.168.10.1 segment, leave it as Host based L2 mode, and if you need Internet access from that segment, just drop a leg of the VM into the 192.168.1.x segment, and slap a Host route on there for internet.


I don't recall if you can run more than 1 LAN in NAT mode under HyperV networking. Otherwise you could just do that.




The other possibility, and this totally depends on whether you have a Layer-3 switch at your disposal (any Cisco 35xx, etc. is fine for this purpose.) But you could just trunk the VHost uplinks to the switch, and create routed interfaces on the switch for inter_VLAN routing.

The benefit here is you could slap some ACLs on those SVIs if you wanted to limit the access between VLANs, all while routing them through the switch.

This would scale to any number of VLANs you'd wanna run on that VHost. And this would be as close to enterprise as you could get, without alot of hardware.

Most Virtual Stacks don't run Layer-3 in the VSwitch anyway. So it would probably be a bad practice to run ICS or something like that on a Windows Server VM, just to get around a limitation of your lab.
 
Ok, so I do not see any layering settings in hyper-v at all. I do not have any L3 switches. So I spent some time googling, there are a lot of suggestions, many of which I tried.

The one I found that just works with little effort: http://social.technet.microsoft.com...895b09/route-2-networks?forum=winserverhyperv

I'll share some more details should others care to do this on their own as well:

So basically I setup:
1 virtual switch called vlab.private. This is bound to an Intel nic(not plugged in yet), 192.168.10.1/24
1 virtual switch called ext.VirtualSwitch. This is bound to an LACP group, 192.168.1.1/24

The ext.VisrtualSwitch is set at 192.168.1.2(set gateway/dns)
The vlab.private is set at 192.168.10.2(no gateway, no dns)

Now this will enable a dhcp server on RRAS. You can disable DHCP here and then have the gateway of your DC(or whatever) is handing out DHCP to use the ip of the vlab.private to access the other network.


I stood up a win2k8r2 VM and installed RRAS, then
 
You must log in or register to reply here.
Back
Top