From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <000001cad5e4$fcc81030$f6583090$@com> References: <000001cad5e4$fcc81030$f6583090$@com> Date: Tue, 6 Apr 2010 19:08:35 -0600 Message-ID: From: Robert LeBlanc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Bridge] Bridging vSwitches in VMwares ESXi List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ryan King Cc: bridge@lists.linux-foundation.org On Tue, Apr 6, 2010 at 5:57 PM, Ryan King wrote: > I've also had the exact same issues. =A0However, if I move one of the vNI= Cs to > a vSwitch using a different physical nic, then the issue seems to go away= . In my experience, as long as you only have on pNIC per vSwitch, it works just fine. As soon as you add a second pNIC to the vSwitch, it creates a loop and confuses the linux bridge (you can watch the MAC bounce between ports if you do a standard ping from one machine and a broadcast ping from another machine). We were using Broadcom NICs. Robert LeBlanc Life Sciences & Undergraduate Education Computer Support Brigham Young University