- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We're deploying a few NUC13ANKi5 NUCs to replace some older NUCs.
The NUC13ANKi5 includes the i226-V Ethernet adapter.
We need to be able to set up multiple VLANs using the PROSet utility (or the PowerShell commands).
After installing the latest driver we could find, as well as PROSet, it looks like the i226-V isn't supported in PROSet, and we can't configure multiple VLANs on the adapter.
Is this expected? Is there a specific version of the driver and PROSet utility that will let us configure multiple VLANs? Our older NUCs have the i219-V and older network adapters.
I can't find any actual documentation that says which network adapters support VLAN configuration via the PROSet utility and which don't.
The I219 does support multiple VLAN configuration through PROSet, but the product brief for the I219 doesn't mention VLAN or 802.1q anywhere.
https://www.intel.com/content/www/us/en/content-details/333229/intel-ethernet-connection-i219-product-brief.html
The I226 doesn't seem to support multiple VLAN configuration through PROSet, and the product brief for the I226 still doesn't mention VLAN or 802.1q anywhere.
https://www.intel.com/content/www/us/en/content-details/621753/intel-ethernet-controller-i225-i226-product-brief.html
The Adapter User Guide for Intel Ethernet Adapters doesn't mention it at all either.
https://www.intel.com/content/www/us/en/download/19373/adapter-user-guide-for-intel-ethernet-adapters.html
The "This download is valid for the product(s) listed below." section list some older adapters, up to the 218, but it does not list the 219, which does support multiple VLAN configuration through PROSet.
Further, the user guide itself makes no mention of the 219 other than to note that the last supported 32-bit driver for Windows 10 was version 25.2.
As far as I can tell, there is no way to actually determine which network adapters / driver versions support multiple VLANs (configured through PROSet or the PowerShell commandlets).
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, I don't believe I have access to the Resource & Design Center.
I know both adapters support VLAN tagging. That is not the question. Nearly every single Ethernet adapter has basic VLAN functionality.
The question is whether or not Intel allows you to create multiple virtual adapters within the guest OS that each have different VLAN IDs. This is simple to do on older adapters using Intel PROSet, or PowerShell.
Your last link is a very old reference regarding how to use the PowerShell commandlets to do this. This was necessary years ago when Microsoft broke the old method of assigning VLANs through the adapter properties dialog window. Intel later updated the functionality and folded it back into PROSet, where it has worked without issue for the last few years. (The only issue I ran into was the fact that you had to recreate the VLANs after the major Windows updates. This is Microsoft's fault, and not a big deal.)
It seems like Intel has abandoned Intel PROSet for Windows 11, but still officially supports it for Windows 10.
I am here to tell you that the I226 and Intel PROSet on Windows 10 are not actually supported, even though there is a Windows 10 driver for the I226. Within PROSet, you cannot configure VLANs or teaming on the I226. PROSet simply tells you that it is not compatible.
Regardless, the solution to my problem is to use the Hyper-V functionality built into Windows. As long as your network adapter and driver support VLANs, then you should be able to do this.
See https://community.intel.com/t5/Ethernet-Products/Creating-Vlans-with-the-ProSet-utility-in-windows-11-not-working/m-p/1306141 and https://taeffner.net/2022/04/multiple-vlans-windows-10-11-onboard-tools-hyper-v/.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @sbmi1,
Thank you for posting in Intel Ethernet Communities.
Unfortunately, i226-V behavior is expected because isn't supported in PROSet.
You may refer to this article for network adapters support PROSet , and with summary from the Adapter User Guide that provide overall information update.
Can you confirm if you have an account to Resource & Design Center? If yes, you may refer to link below for the Technical Library of Intel® Ethernet Controller I226 & I219 and to get design documents, drivers, datasheets, release notes & more for the Intel® Ethernet Controller I226 & I219 .
The datasheets provide exclusive info that both I226 & I219 have 802.1q VLAN support feature
In case you don't have access, the RDC Account Support form is the channel to process your account update process or report any problems with the provided sites. You should fill out the form stated on the following website:
https://www.intel.com/content/www/us/en/forms/support/my-intel-sign-on-support.html
For specific Instructions on how to use PowerShell* with recent drivers to set up a team with an Intel® Ethernet Adapter, please see: How to Set Up Teaming with an Intel® Ethernet Adapter in Windows® 10 1809?
I hope this helps with your inquiry.
Best regards,
BY_Intel
Intel Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, I don't believe I have access to the Resource & Design Center.
I know both adapters support VLAN tagging. That is not the question. Nearly every single Ethernet adapter has basic VLAN functionality.
The question is whether or not Intel allows you to create multiple virtual adapters within the guest OS that each have different VLAN IDs. This is simple to do on older adapters using Intel PROSet, or PowerShell.
Your last link is a very old reference regarding how to use the PowerShell commandlets to do this. This was necessary years ago when Microsoft broke the old method of assigning VLANs through the adapter properties dialog window. Intel later updated the functionality and folded it back into PROSet, where it has worked without issue for the last few years. (The only issue I ran into was the fact that you had to recreate the VLANs after the major Windows updates. This is Microsoft's fault, and not a big deal.)
It seems like Intel has abandoned Intel PROSet for Windows 11, but still officially supports it for Windows 10.
I am here to tell you that the I226 and Intel PROSet on Windows 10 are not actually supported, even though there is a Windows 10 driver for the I226. Within PROSet, you cannot configure VLANs or teaming on the I226. PROSet simply tells you that it is not compatible.
Regardless, the solution to my problem is to use the Hyper-V functionality built into Windows. As long as your network adapter and driver support VLANs, then you should be able to do this.
See https://community.intel.com/t5/Ethernet-Products/Creating-Vlans-with-the-ProSet-utility-in-windows-11-not-working/m-p/1306141 and https://taeffner.net/2022/04/multiple-vlans-windows-10-11-onboard-tools-hyper-v/.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @sbmi1,
Thank you for the information, and we're glad you found the solution. May I know if there is anything else I can help with?
Best regards,
BY_Intel
Intel Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @sbmi1,
Please be informed that we will now close this request since we haven't received any response from our previous follow ups. Just feel free to post a new question if you may have any other inquiry in the future as this thread will no longer be monitored.
Thank you again.
Best regards,
BY_Intel
Intel Customer Support
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page