HUNSN RJ46, 6 x 2.5GbE I226-V - VLAN problem
-
Hello,
I purchased the HUNSN RJ46 with an I226-V and I'm experiencing issues with VLAN tagging.
Here's my setup:
- pfSense is installed via Hyper-V on Windows 11 Pro (I tried Windows Server, but, to my surprise, there are no drivers for the I226-V).
- I have configured VLANs on pfSense.
- The trunk mode is set for the Hyper-V virtual adapter. It works internally; that is, the pfSense virtual machine and the host can communicate via a VLAN-tagged network (Enable virtual LAN identification for the management operating system).
The issue is that, even though the virtual adapter is set in trunk mode, no tagged traffic is being sent or received through the physical I226-V NIC. Am I missing something or is it I226-V?Has anybody had the same problem?
Thanks
-
Does it pass untagged traffic?
Does it pass tagged traffic if you install pfSense bare metal on it directly?
I've never seen a VLAN issue on the i226-V NICs we use in our own devices. This seems likely to be a Windows/Hyper-V issue.
-
Does it pass untagged traffic?
It does.
Does it pass tagged traffic if you install pfSense bare metal on it directly?
I haven't tested it on bare metal.
This seems likely to be a Windows/Hyper-V issue.
I've done similar setups multiple times on different hardware without any problem. Maybe it's the issue of Windows 11 Pro drivers for i226-V. I have read that Intel is not happy with consumer-grade NICs being used in "advanced" scenarios. That's why there are no drivers for i226-v for Windows Server. Maybe it got VLAN support chopped off.
-
Possible but it seems unlikely. You can do VLANs in software even if the drivers don't expose any hardware capabilities.