I spent HOURS scratching my head on why I could not get VLANS working on OPNsense via Hyper-V. After isolating and troubleshooting each individual component, I figured that the OPNsense VM was not seeing the tagging. I almost ended up going bare metal, thankfully I saw your video and that saved me! THANKS SO MUCH!!!
Firstly thanks for explain the HyperV Clan concept. My setup is typical like you setup, however excludes an external physical switch as in your case. I set up a vlan attached it to Lan (as you explain), however when I tag the hyperV client network with this vlan number it doesn't want to acknowledge and lease the vlan ip address, instead it defaults to un-identified network. There is an option in opnsense I think it's called vxlan do you know if this might be the way out?
I spent HOURS scratching my head on why I could not get VLANS working on OPNsense via Hyper-V. After isolating and troubleshooting each individual component, I figured that the OPNsense VM was not seeing the tagging. I almost ended up going bare metal, thankfully I saw your video and that saved me! THANKS SO MUCH!!!
Firstly thanks for explain the HyperV Clan concept. My setup is typical like you setup, however excludes an external physical switch as in your case. I set up a vlan attached it to Lan (as you explain), however when I tag the hyperV client network with this vlan number it doesn't want to acknowledge and lease the vlan ip address, instead it defaults to un-identified network. There is an option in opnsense I think it's called vxlan do you know if this might be the way out?
actually your explanation after review made sense, my setup worked just fine after creating those vlan interfaces in hyperV. Thanks
does it need to be mapped to a physical adapter? does it not work with a team?