Using VLAN ID 1 (was: CARP under Hyper-V: weird things happen)

[Stefan Bethke]

Only tangential to your main issues, but:
> Am 31.05.2020 um 18:07 schrieb Eugene M. Zheganin <emz at norma.perm.ru>:
> 
> Another weird this is that vlan1  is refusing to work (seems like packets are never received on the VM side) unless its configured on another adapter in the -Untagged (once again powershell term for SetVmNetworkAdapterVlan).

I believe it is best practice to not use VLAN ID 1 in your network design because many vendors assign it a special role, and it can be hard to reconfigure that on the devices. The virtual switch might have the same issue.

Stefan

-- 
Stefan Bethke <stb at lassitu.de>   Fon +49 151 14070811