Date: Fri, 21 Aug 2015 10:25:05 +0200 From: Marko =?UTF-8?B?Q3VwYcSH?= <marko.cupac@mimar.rs> To: freebsd-stable@freebsd.org Subject: Re: vmx and esxi vst mode vlan tagging Message-ID: <20150821102505.7febb5b0@efreet> In-Reply-To: <20150820132353.2ae19568@efreet> References: <20150820132353.2ae19568@efreet>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Aug 2015 13:23:53 +0200 Marko Cupa=C4=87 <marko.cupac@mimar.rs> wrote: > Hi, >=20 > I have just spent half an hour bashing my head against the wall why my > FreeBSD-10.2-RELEASE i386 machine with kernel-included vmx driver and > emulators/open-vm-tools installed won't ping machines on the other > vlan on the same vSwitch. It DOES ping other virtual machines on the > same vSwitch and same vlan (freebsd servers), and it DOES ping > physical machines in other vlans. It DOES NOT ping virtual machines > on the same vSwitch and different vlan (windows servers). >=20 > To cut the long story short, it appears that the problem is on FreeBSD > side, as another machine (FreeBSD-10.1-RELEASE-p14 amd 64) with vmx3f0 > driver and VMWare's vmware-tools installed pings everything as it > should. >=20 > Could it be that FreeBSD's vmx driver does not support all the > functions of vmware's vmx3f driver? I deleted open-vm-tools and installed vmware-tools, but the broblem remains. I'm gonna test if 10.2-RELEASE amd64 has the same issue. That should tell me if problem is related to difference between i386 and amd64 in 10.2-RELEASE. If not, could this be a regression in 10.2? Should I report a bug or do some more testing? Thank you in advance, --=20 Marko Cupa=C4=87 https://www.mimar.rs/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150821102505.7febb5b0>