No VLAN traffic being seen with DDA NIC in Hyper-V
-
I'm using Direct Device Assignment in Hyper-V to pass two out of four NIC (Intel X710-T4L) ports to the pfSense VM. It works, but now I can't access anything on VLANs. I've done packet captures on the VLAN interfaces with pfSense, and there is no traffic. I have Ubiquiti switches. IoT devices, for example, are on VLAN 20, and the switch (USW-Flex-Mini) ports they're connected to have VLAN 20 as the primary network. External servers are on VLAN 10. They run as guests under Hyper-V on a different machine. The virtual NICs of those guests are configured to use VLAN 10, and the switch (US-8-60W) ports they're connected to have a traffic restriction in place that allows VLAN 10, and my ordinary LAN is primary.
When pfSense was using the Hyper-V virtual NICs, I needed to configure the LAN virtual NIC port as a trunk with
Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "1,10,20" -NativeVlanId 0With Direct Device Assignment, pfSense has two of the physical NIC ports, so I don't think there is anything similar that needs to be done, is there?
Am I missing something?
Thanks!
-
@andrew_241 said in No VLAN traffic being seen with DDA NIC in Hyper-V:
Am I missing something?
No, but haven't use DDA lately.
I find it more versatile to use those virtual NICs -
Looks like I was missing something: no client on these VLANs were getting DHCP (IPv4) assignments. They did, however, have active IPv6 addresses. Apparently, DHCP snooping was enabled on all the switches, and disabling it solved the problem. I noticed this shortly after posting.
