From owner-freebsd-bugs@FreeBSD.ORG  Wed May  6 21:05:05 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C5B70CF1
 for <freebsd-bugs@FreeBSD.org>; Wed,  6 May 2015 21:05:05 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B08681DA4
 for <freebsd-bugs@FreeBSD.org>; Wed,  6 May 2015 21:05:05 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t46L55aF097328
 for <freebsd-bugs@FreeBSD.org>; Wed, 6 May 2015 21:05:05 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 198406] More than 4 esxi vmxnet3 interfaces causes vlans
 attached to vmxnet interfaces to stop working
Date: Wed, 06 May 2015 21:05:04 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: timothyyl@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-198406-8-9vIt1Cdgt5@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198406-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-198406-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 May 2015 21:05:05 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406

--- Comment #2 from timothyyl@gmail.com ---
I believe I am seeing something very similar. In my case, everything works fine
until I add a 5th interface, at which point nothing on that interface will
work. The other interfaces continue to pass traffic, however. This essentially
means that pfsense in VMware is useless if you plan on using one interface per
port group and letting VMware do the tagging, since many places have greater
than 5 VLANs in use. Any suggestions?

-- 
You are receiving this mail because:
You are the assignee for the bug.