I think I just sorted it all out!
To let pfSense run on Hyper-V hosted on single network adapter Intel NUC with multiple VLANs, and together with virtual machines as well as other local Windows services and programs, I took following steps:
Run PowerShell as Administrator Run: Set-VMNetworkAdapterVlan -VMName pfSense -Trunk -AllowedVlanIdList 10-100 -NativeVlanId 1note: pfSense is the name of Virtual Machine and AllowedVlanIdList covers range of VLANs configured for pfSense. NativeVlanId is left with default ID=1
more about PS command: https://docs.microsoft.com/en-us/powershell/module/hyper-v/set-vmnetworkadaptervlan?view=win10-ps Change Hyper-V Virtual Switch to enable VLAN = 10 (as configured on port 1 of the TP-Link managed switch - see my first post).
note: do not enable any VLAN identification on Virtual Network card configured for pfSense. Change for all other virtual machines VLAN to 10 (do not enable VLAN inside virtual machine - leave default VLAN ID = 0)
Final VLAN configuration as per component:
Intel NUC network card - no change, default config (no VLAN) Hyper-V Virtual Switch - enable VLAN = 10 pfSense virtual machine Network Adapter VLAN disabled every other Hyper-V virtual machine's Network Adapter VLAN = 10 no need to configure or change anything for DockerI'm yet to test this configuration so any comments welcome.
Screenshot for reference.
0_1539058300648_50f60e35-81d1-4887-80d7-2eaccf3b4efa-image.png