Windows and its missing tagged VLAN Feature
Dear Microsoft, dear Community! I've been hoping and waiting for a tagged vlan feature built in to windows since... a decade? maybe two... I don't understand why, as of 2025, there still is a requirement for driver support or hyper-v vm nics in order to add multiple tagged vlan interfaces to a system? Its kind of my daily work to connect to several vlans via trunk ports. Linux, FreeBSD even MacOS: no problem at all. Why cant we get that functionality? I really wish that would make it to Windows: Is there any chance? I guess I am not the only one missing that feature. Kind regards P.s.: I don't mean to rant, I just don't have the necessary knowledge to understand why its so complicated or maybe even undesired to get that functionality built into the OS.
Server 2022 Hyper-V and multiple VLANs across single SET
What is the best way to configure two IPs on separate VLANs going over a single Switch Embedded Team (i.e. the same physical NICs handling both storage and VM network traffic) for a standalone Server 2022 Hyper-V host? From what I've read I just need to add multiple vNICs to my SET vSwitch and assign each a VLAN (Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName iSCSI -Access -VlanId 10) but it's not working in my simulator (GNS3). The tagged traffic isn't being passed by the switches (the ports on the switches are port-channeled and trunked for the two VLANs). I'm not sure at this point if it's a switch or Windows configuration issue, a limitation of Windows Server in GNS3, or a limitation of Windows Server itself. I'm trying to simulate this prior to an actual physical deployment, and want to get it right in testing so I can hopefully avoid any networking issues on the day. Thanks.