On Fri, Aug 21, 2015 at 10:25:05AM +0200, Marko Cupa'c wrote:
> On Thu, 20 Aug 2015 13:23:53 +0200
> Marko Cupa'c <marko.cupac at mimar.rs> wrote:
>
> > Hi,
> >
> > 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).
> >
> > 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.
> >
> > 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?
netstat -nr
arp -na
ifconfig -a
ping's commands and results.