From owner-freebsd-stable@freebsd.org Fri Aug 21 10:19:18 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 171519BEF3A for ; Fri, 21 Aug 2015 10:19:18 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from smtp.mimar.rs (smtp.mimar.rs [193.53.106.135]) by mx1.freebsd.org (Postfix) with ESMTP id BAE96B0C for ; Fri, 21 Aug 2015 10:19:16 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from vscan.mimar.rs (vscan.mimar.rs [193.53.106.134]) by smtp.mimar.rs (Postfix) with ESMTP id 9825A89A82; Fri, 21 Aug 2015 12:19:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mimar.rs; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:organization:references:in-reply-to:message-id:subject :subject:from:from:date:date:received:received; s=mimar-0901; t= 1440152352; x=1441966753; bh=+Vk2f1gDWAyF1rLbRBhm/Lb/iXDL3V5T4Y/ bodh1IoE=; b=Hh4uh3V7MmzRZXtgTkdnb8hpewWCZiwpos6E/g+GtBgfAhG/Ya0 yP2XlcbX5fwGRuD7UB02xHecJ258waJ953CXbGNCDl4Ro6YbnIRa764OEDpPG6wI V8XgOeoRRouu1QMeR58nmG62QxxMN9/do4yGJLcurDvD3UMV7wKm1SjA= X-Virus-Scanned: amavisd-new at mimar.rs Received: from smtp.mimar.rs ([193.53.106.135]) by vscan.mimar.rs (vscan.mimar.rs [193.53.106.134]) (amavisd-new, port 10026) with ESMTP id JLXY4-JILaWv; Fri, 21 Aug 2015 12:19:12 +0200 (CEST) Received: from efreet (unknown [193.53.106.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: marko.cupac@mimar.rs) by smtp.mimar.rs (Postfix) with ESMTPSA id C0DC689691; Fri, 21 Aug 2015 12:19:11 +0200 (CEST) Date: Fri, 21 Aug 2015 12:19:11 +0200 From: Marko =?UTF-8?B?Q3VwYcSH?= To: Slawa Olhovchenkov Cc: freebsd-stable@freebsd.org Subject: Re: vmx and esxi vst mode vlan tagging Message-ID: <20150821121911.47728de0@efreet> In-Reply-To: <20150821094102.GI3158@zxy.spb.ru> References: <20150820132353.2ae19568@efreet> <20150821102505.7febb5b0@efreet> <20150821094102.GI3158@zxy.spb.ru> Organization: mimar X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Aug 2015 10:19:18 -0000 On Fri, 21 Aug 2015 12:41:02 +0300 Slawa Olhovchenkov wrote: > On Fri, Aug 21, 2015 at 10:25:05AM +0200, Marko Cupa'c wrote: >=20 > > On Thu, 20 Aug 2015 13:23:53 +0200 > > Marko Cupa'c wrote: > >=20 > > > 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? > >=20 > > 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? > >=20 > > Should I report a bug or do some more testing? >=20 > netstat -nr > arp -na > ifconfig -a > ping's commands and results. Sorry guys, please dismiss this issue entirely. I was constantly setting /24 subnet mask whereas the correct mask for the vlan is /27. Please consider the fact that my long-needed vacation starts tomorrow :) Regards, --=20 Marko Cupa=C4=87 https://www.mimar.rs/