In this article, we will show how to configure a Tagged VLAN Interface On Windows 10/11 and Windows Server 2019 (2022/2016/2012R2). VLAN (Virtual LAN) described in the specification IEEE 802.1Q Includes marking traffic with standard and tags (vlanid) so that a network packet can be sent to a particular virtual network. VLANs are used to isolate and segment networks, to restrict broadcast domains, and to isolate network segments to improve security. On Windows, you can configure multiple logical network interfaces with different VLAN IDs on the same physical NIC using different devices.
To use VLANs on Windows, you need to reconfigure the physical switch port to which your computer/server is connected. port must be switched from access mode trunk mode, By default, all VLANs are allowed on the trunk port, but you can set a list of allowed VLAN numbers (1 To 4094) is available on this Ethernet switch port.
Creating Multiple VLAN Interfaces on Windows 10 and 11
Windows desktop versions do not natively support VLAN tagging. By default, most network adapter drivers ignore all VLAN tags in network packets and external VLANs become unreachable.
For some network adapters, you can set the VLAN number in the driver properties:
- Run Device Manager (
- expand the network adapters Open the section and properties of your network adapter;
- go to advanced tab and find VLAN ID alternative;
- You can set VLAN number here;
- For some NICs, you must first enable it Packet Priority and VLAN alternative.
In modern versions of Windows 10 and 11, you can set a VLAN tag for network interface adapters. You can use PowerShell to manage network settings. For example, you want to set VLAN ID 24 for your network interface named ethernet0:
Set-NetAdapter –Name "Ethernet0" -VlanID 24
For some NICs (from Intel, Broadcom, HP, Realtek), special tools are available that allow you to create a virtual network interface in Windows with a VLAN ID. To do this, you need to install a special driver on your computer that supports 802.1Q tagged traffic and the official configuration tool from the vendor.
Create Multiple VLANs on Realtek NIC in Windows 10 or 11
For Realtek NICs, you can configure multiple virtual NICs with different VLANs Realtek Ethernet Diagnostic Utility, Find the details of your Realtek network controller on the vendor’s website, and check that this model supports VLANs. For example, the specification of the RTL8169SC(L) network controller has this option:
Supports IEEE 802.1Q VLAN tagging
Download and install and run the latest network drivers for your Realtek adapter Realtek Ethernet Diagnostic Utility (Diagnostic program for Win7/Win8/Win10/Win11).
go to VLAN section, click add add more required VLAN ID, After that, a new network interface will appear in Windows.
After creating network interfaces for your VLAN, you can assign IP addresses from the respective IP networks.
How to setup VLAN on Intel Ethernet Network Adapter?
Intel’s own Intel Advanced Network Services (Intel® ANS) Tools for configuring VLAN interfaces. Your network adapter model must, of course, support VLANs (for example, VLANs are not supported for NICs such as the Intel Pro/100 or Pro/1000). When installing the driver, select Intel ProSet for Windows Device Manager And advanced network services alternative.
Then a separate VLAN tab appears in the properties of your physical Intel network adapter, where you can create multiple VLAN interfaces.
However, this method works on all previous versions of Windows (Windows 10 up to 1809). In modern Windows 10/11 builds, the following message is displayed in the VLAN tab:
Intel(R) Advanced Network (Intel(R) ANS) Teams and VLANs are not supported on Microsoft Windows 10.
Intel recently released new network adapter drivers and the Intel ProSet Adapter Configuration Tool for the latest builds of Windows 10 and 11. Download and install the latest Intel drivers and Intel ProSet utility.
Run the Configuration Tool, go to Teaming/VLAN tab, click new button, and specify the name of the network interface and its vlanid,
Also you can add/remove/view the list of VLANs on Intel NICs. IntelNetCmdlets Modulus. Import the module into your PowerShell session:
Import-Module -Name "C:\Program Files\Intel\Wired Networking\IntelNetCmdlets\IntelNetCmdlets" -Scope Local
You can create an unmarked virtual network adapter (usually used with native-vlan-id):
Add-IntelNetVLAN -ParentName "Intel(R) Ethernet Connection I219-LM" -VLANID 0
To create an Intel NIC with a unique VLAN number:
Add-IntelNetVLAN -ParentName "Intel(R) Ethernet Connection I219-LM" -VLANID 103
To list all virtual Intel network adapters:
Remove VLAN interface:
Remove-IntelNetVLAN -ParentName "Intel(R) Ethernet Connection I219-LM" -VLANID 103
For Broadcom NICs, you can create groups of virtual network interfaces and assign VLAN IDs Broadcom Advanced Control Suite tool.
How to configure multiple VLANs on Windows Server 2022/2019/2016?
In Windows Server 2022/2019/2016/2012R2, you can configure multiple VLANs on the same network interface using built-in tools (without installing third-party drivers and tools). Let’s try to configure multiple VLANs on the same physical NIC in Windows Server 2019 NIC Teaming,
- open server Manager , local and click NIC Teaming Contact,
- In teams section, click Work , New Team, specify the name of the group and select the network adapter to add;
- in again”Adapters and Interfaces“Section, Add Virtual Network Interface. Click Work -> add interface;
- Enter the name of the interface you are going to create and a VLAN number;
You can add a network interface and set a VLAN for it in PowerShell:
Add-NetLbfoTeamNic -Team vTeam -VlanID 24 -Name VLAN24
- Similarly, you can add as many VLAN network interfaces as you want;
Please note that Windows Server 2022/2019/2016 supports up to 32 NICs (and unique VLANs) per NIC teaming group.
- A separate virtual network adapter will appear in the list of network connections
- Now you can configure the IP settings for each VLAN interface in the properties of the network adapter or by using the PowerShell cmdlets:
New-NetIPAddress -InterfaceAlias your_VLAN_interface -IPAddress 192.168.10.10 -PrefixLength 24 -DefaultGateway 192.168.10.1
Set-DnsClientServerAddress -InterfaceAlias your_VLAN_interface -ServerAddresses 192.168.100.12
Create Multiple VLANs With Windows Hyper-V Role
You can programmatically handle multiple VLANs in Windows via the Hyper-V subsystem (available in both Windows Server and Desktop Windows 10/11 Pro and Enterprise editions). You can create virtual switches with network adapters in a specific VLAN.
To do this, you need to install Hyper-V components:
Enable-WindowsOptionalFeature -Online -FeatureName:Microsoft-Hyper-V -All
Create a new virtual switch through Hyper-V Manager or by using PowerShell commands (see an example in the article on how to configure a Hyper-V server).
Then run the following command for each VLAN you want to create:
Add-VMNetworkAdapter -ManagementOS -Name VLAN24 -StaticMacAddress "11-11-AA-BB-CC-DD" -SwitchName vSwitch2
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName VLAN24 -Access -VlanId 24
So the VLAN you want a network adapter with will show up in Windows.
If you have VMs running on your Hyper-V server, you can put them in different VLANs. To switch the VM’s virtual network adapter to access mode on Hyper-V and allow it to receive traffic only with a specific VLAN ID, use the command:
Set-VMNetworkAdapterVlan -VMName MyVMName1 -Access -VlanId 30
Display a list of VMs and their assigned VLANs:
In Windows Server 2022 with the Hyper-V role, you will not be able to force a virtual switch for such teaming interfaces. The fact that LBFO NIC teaming is a deprecated feature on Windows Server 2022 (https://aka.ms/lbfodeprecation) instead of NIC teaming, it is proposed to use Switch Embedded Teaming ,group,
Let’s create a virtual adapter and assign it a VLAN on Windows Server 2022 Hyper-V using SET.
Create a virtual switch connected to the host’s physical adapter:
New-VMSwitch -Name HVVLANSwitch1 -NetAdapterName "Ethernet3","Ethernet4" -EnableEmbeddedTeaming $true
Now create a virtual adapter connected to the virtual switch:
Add-VMNetworkAdapter -ManagementOS -Name "VLAN22" -StaticMacAddress "XX-XX-XX-XX-XX-XX" -SwitchName HVVLANSwitch1
Assign a VLAN tag to your virtual adapter:
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "VLAN22" -Access -VlanId 22
You can enable Virtual Hyper-V Adapter to receive packets from multiple VLANs using the command:
Get-VMNetworkAdapter -Name youradaptername | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList 40-69 -NativeVlanId 0
-NativeVlanId 0 parameter is required. In this case, we tell Hyper-V that VLAN: 0 Used as native for untagged traffic.