Vlan for Windows 10
-
It seems that Intel has not produced driver software for Windows 10 that supports Vlans via the installed network interface card.
I would like to access various vlans from my management workstation but can't. Any observations or ideas? Does any one know when Intel will start supporting Windows 10 with Valns? -
They won't.
Your only choice to get vlans (with any NICs) is to install Hyper-V role.
That will allow you to add Hyper-V virtual adapters and tag them with VLANs (powershell needed).
-
Thanks for the update. you gave the answere I did not wish to receive. It is unfortunate the vendors will not work together. I will embark on the route you suggest.
Best To You…
-
Why can you not access these vlans from your "management" station?
Why are you wanting to create extra networks and tag them at the client? Why would you not just put your management station in the management vlan. Or just at your firewall allow that management stations IP no matter what vlan its in to access the other vlans..
Been in the field for many a year, and have never seen tagging done at the management station as way to access other vlans. That by design would defeat the whole purpose of firewall between your vlans. Might as well just multi home it and put multiple nics on each layer 2..
-
From Intel site:
Detailed Description
Creating Intel ANS teams and VLANs on Windows
10 is currently not supported. As a result, when created, teams and VLANs do not pass traffic. We expect that ANS will be supported on Windows 10 client in a future release.https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10
-
Why can you not access these vlans from your "management" station?
Why are you wanting to create extra networks and tag them at the client? Why would you not just put your management station in the management vlan. Or just at your firewall allow that management stations IP no matter what vlan its in to access the other vlans..
Been in the field for many a year, and have never seen tagging done at the management station as way to access other vlans. That by design would defeat the whole purpose of firewall between your vlans. Might as well just multi home it and put multiple nics on each layer 2..
There may be exceptional cases when it is needed to "hack" the firewall. Multicast audio/video streams for example cannot pass through pfSense (and in many applications they shouldn't) but equipment management in such a network, including testing those streams, may require LayerII presence, and access to other networks in the same time.
-
They won't.
Your only choice to get vlans (with any NICs) is to install Hyper-V role.
That will allow you to add Hyper-V virtual adapters and tag them with VLANs (powershell needed).
Bummer, but good to know. I was going to upgrade my workstation @ the office to Windows 10 but I bring a few VLANs into it (for running virtual machines on different segments) and I guess I'll have to wait.
-
"but I bring a few VLANs into it (for running virtual machines on different segments)"
That is a valid reason.. But what does that have to do with the OS wouldn't that be controlled at the VM software?
"There may be exceptional cases when it is needed to "hack" the firewall."
exceptional for sure - 25 some years in biz, and never had such a requirement. If you needed something to be on a specific vlan, you can just use a different device on that vlan other than your "management" pc ;)
-
Bummer, but good to know. I was going to upgrade my workstation @ the office to Windows 10 but I bring a few VLANs into it (for running virtual machines on different segments) and I guess I'll have to wait.
Not much point waiting. Even with Server 2012 R2, you're expected to use M$ tools to run VLANs (by setting up a single NIC in a LBBO Team and assigning VLANs to it).
It's not exactly a bad idea since not all network chip manufacturers provide tools to configure VLANs and/ or link aggregation.
The only issue is that with Windows 10, you can't configure VLANs without Hyper-V role. That means your processor on the workstation will never clock down - Hyper-V forces the processor to always run at the maximum clockspeed to reduce impact on the VMs. Probably not a problem for desktops but it's an issue for laptops.
