vlan to the windows Guest

[akrammokhtar]

i am on a cisco switch my port is trunk
and another port have DHCP for VLAN 208 for example
my guest os is windows 11 and it cannot get the ip address from dhcp of vlan 208
my question is how to configure virtualbox to have the bridged Ethernet on vlan 208.

so my laptop host windows will be vlan1
and my virtualbox guest os windows 11 will be vlan208?
will it work on virtualbox like i did it before on same laptop by hyperv and esxi too

[scottgus1]

First, check if Bridged will work without trying VLANs. Bridged does not always work over Wi-Fi.

If Bridged works non-VLAN, then try a web-search:

bridged vlan site:forums.virtualbox.org

A few topics come up with ideas, like viewtopic.php?f=1&t=101010#p519501 and viewtopic.php?f=6&t=69547

[akrammokhtar]

1st i want to use it in the Ethernet not the wifi
2nd i'lll check the two posts that might help
and post the results

[akrammokhtar]

1st i want to use it in the Ethernet not the wifi
2nd i'lll check the two posts that might help
and post the results

i tried both and i found out that the vlan does not passthrough virtualbox at all

the only solution i know is the make hyperv vswitch with three powershell commands to have vlan on it
here is the three lines
Run powershell as administrator
then type
New-VMSwitch -Name "External_network" -NetAdapterName "Ethernet"
then type
Add-VMNetworkAdapter -ManagementOS -Name VLAN10 -SwitchName External_network
then type
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName VLAN10 -Access -VlanID 10

and thats it
it will work with ur virtualbox

[scottgus1]

That's as I saw things in the links above: a host OS bridge of some sort that can handle VLANs with appropriate filtering, then have Virtualbox Bridge to that host bridge.

[akrammokhtar]

That's as I saw things in the links above: a host OS bridge of some sort that can handle VLANs with appropriate filtering, then have Virtualbox Bridge to that host bridge.

Exactly ,so VirtualBox does not have it like hyperv Virtual switch ,so we use it to VirtualBox
you only need to check two things in windows features
1 - Hyper-V Module For Windows Powershell
2- Hyper-V Services

[BillG]

If it works with the Hyper-V default switch, it should work with VirtualBox NAT, not bridged at all. The default switch is just an implementation of Windows ICS which they put into the desktop version of Hyper-V to allow it to share the host's Internet connection (as VMWare and VirtualBox do). The original version of Hyper-V was for Windows Server and did not give a vm Internet access by default.

Are you saying that using VirtualBox NAT in the vm gives you a different IP from when you use the Hyper-V default interface? If that is the case it would certainly suggest to me that one is seeing the VLAN tag and the other is not.

Do you have more than one NIC in the host OS? If so, how are they configured? That would be the only way to use bridging to get around the problem.

[akrammokhtar]

If it works with the Hyper-V default switch, it should work with VirtualBox NAT, not bridged at all. The default switch is just an implementation of Windows ICS which they put into the desktop version of Hyper-V to allow it to share the host's Internet connection (as VMWare and VirtualBox do). The original version of Hyper-V was for Windows Server and did not give a vm Internet access by default.

Are you saying that using VirtualBox NAT in the vm gives you a different IP from when you use the Hyper-V default interface? If that is the case it would certainly suggest to me that one is seeing the VLAN tag and the other is not.

Do you have more than one NIC in the host OS? If so, how are they configured? That would be the only way to use bridging to get around the problem.

Are you saying that using VirtualBox NAT in the VM gives you a different IP from when you use the Hyper-V default interface? If that is the case it would certainly suggest to me that one is seeing the VLAN tag and the other is not.

no I understand VirtualBox NAT do, my plan with to make my VirtualBox Guest windows os get VLAN Tag,so it can be isolated by VLAN, which it give another Range of ip depend on the Vlan Subnet,got me

Do you have more than one NIC in the host OS? If so, how are they configured? That would be the only way to use bridging to get around the problem.

just one NIC and one WIFI it's my Laptop on windows 11 Host OS , i'm not looking for only Bridging,i was looking for VirtualBox Guest windows os get VLAN Tag, so it can be isolated by VLAN ,thatz it

[BillG]

Sorry about introducing the Hyper-V default adapter into this. I misread what you had written.

What you have done is set up a virtual interface in the host. You used Hyper-V and Powershell to create the virtual interface because you had Hyper-V installed on your previous host PC and know how to use it.

That seems to be a simpler solution than the one suggested by Heckfy in the other post on VLANs referred to above. What do you think, Scott?