Date: Mon, 1 Jun 2020 11:18:24 +0200 From: Stefan Bethke <stb@lassitu.de> To: "Eugene M. Zheganin" <emz@norma.perm.ru> Cc: freebsd-stable@freebsd.org Subject: Re: Using VLAN ID 1 (was: CARP under Hyper-V: weird things happen) Message-ID: <9E3AE75F-E3B5-47CD-B472-6DE99116E8D1@lassitu.de> In-Reply-To: <ed9180b4-fe2c-d516-af9d-cade780885f7@norma.perm.ru>
index | next in thread | previous in thread | raw e-mail
Only tangential to your main issues, but: > Am 31.05.2020 um 18:07 schrieb Eugene M. Zheganin <emz@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@lassitu.de> Fon +49 151 14070811help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9E3AE75F-E3B5-47CD-B472-6DE99116E8D1>