Hi,

let use assume you have a network adapter with multiple tagged 802.1q vlans on it. Previously, Intel published the Advanced network services. In the past this could be used to create a virtual network adapter for each VLAN id. Unfortunatly the tool is deprected.

Newer Windows version supports the a network teaming function out of the box. This can be used to provide a similar behaviour.

An example. The Network Interface with the tagged vlans is named “trunk”.

Add a new LAN team only with member “trunk”

PS D:\> New-NetLbfoTeam -Name "Trunk Team VLAN ID 66" -TeamMembers "Trunk" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic -confirm:$false

Add a virtual interface for VLAN ID 66

PS D:\> Add-NetLbfoTeamNic -Team "Trunk Team VLAN ID 66" -VlanID 66 -Name "VLAN 66" -confirm:$false

Now the interface is active in VLAN with ID 66.

May be it makes sense to remove some bindings from the teaming interface itself. Because you don’t want to use it a public interface.

PS D:\> Disable-NetAdapterBinding -Name "Trunk Team VLAN ID 66"  -DisplayName "Internet Protocol Version 4 (TCP/IPv4)"
PS D:\> Disable-NetAdapterBinding -Name "Trunk Team VLAN ID 66"  -DisplayName "Internet Protocol Version 6 (TCP/IPv6)"
PS D:\> Disable-NetAdapterBinding -Name "Trunk Team VLAN ID 66"  -DisplayName "File and Printer Sharing for Microsoft Networks"
PS D:\> Disable-NetAdapterBinding -Name "Trunk Team VLAN ID 66"  -DisplayName "Client for Microsoft Networks"

Regards Michael