1

I have Hyper-v Running. What I am trying to do is setup a CentOS firewall box which will forward all traffic to the 2nd VM CentOS box which has an internal adapter and only seen by the 1st VM Box(firewall box).

In Hyper-V you can setup external, internal, and private Virtual Switches. So what I did was setup a Virtual Switch and set it's VLAN ID to 5. On the other 2 Virtual Adapters which are connected to the Virtual Switch I set them to VLAN ID 5 as well.

I am just confused as to how do I create and setup an internal network between these two VMs using the Virtual Switch.

Improve this question
4
  • Your terminology is a bit confusing, but your VMs should not need to be aware of the VLANs at all. Their ports should be "untagged" members of the desired VLAN. The switchgear will take care of tagging/untagging for you. Commented Jul 24, 2014 at 19:17
  • VM's don't have virtual switches. Do you mean that you created two Hyper-V internal Virtual Switches and connected each VM to one of them? Also, why the need for VLAN's on these internal switches? Commented Jul 24, 2014 at 19:19
  • I can't figure out what you are trying to do here. Perhaps you edit the question to actually describe how you want your network to work instead of just giving us the details about what what you have done. Commented Jul 24, 2014 at 20:01
  • Updated the question. Commented Jul 24, 2014 at 20:05

1 Answer 1

Reset to default
1

First Hyper-V Switches do not have a VLAN ID. Hyper-V switches belong to all VLANs. You assign a VLAN to the virtual adapters with VMs and the virtual adapters created for management.

For the sake of simplicity you should generally stick with a single Virtual Switch unless you really need to segregate traffic.

So basically you should setup your External switch, and link it to whatever interfaces you are using for VM traffic.

In your firewall VM you should have two virtual adapters, the virtual adapter you wall use as the outside adapter should be set to the default VLAN, or whatever VLAN you are using for your VMs. It will depend on the configuration of you physical adapters and switch port you are connected with. If you are not doing VLAN trucking on the switch port you are connected with, this should be the default LAN.

The inside adapter from your firewall, and the adapter on the VM that can both be connected the external switch, and they should be be assigned a VLAN ID different from the VLAN assigned to the external adapter of your firewall. This VLAN probably shouldn't already exist on your external network.

So assuming the switch your Hyper-V box connects to isn't doing any trunking and the un-tagged VLAN is the one you want to access your setup would be like this.

  • Hyper-V switch associated with your physical adapters.
  • Firewall VM
    • External adapter left to default VLAN
    • Internal adapter set to a VLAN 30
  • Inside host
    • Adpater set to VLAN 30
Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.