From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <000101cad601$5d42a300$17c7e900$@com> References: <000001cad5e4$fcc81030$f6583090$@com> <000101cad601$5d42a300$17c7e900$@com> Date: Tue, 6 Apr 2010 21:29:12 -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 9:21 PM, Ryan King wrote: > Just to clarify our setup: > > The physical server has 4 physical nics. =A0vswitch1 uses 2 pnics in > active/active. =A0vswitch2 uses 2 pnics in active/active. > > The VM (running openvpn) has a bridge with one vnic on vswitch1 and one v= nic > on vswitch2. =A0Since moving the 2nd interface to vswitch2, I have not > experienced this issue any more (ie: previously, both vnics were on vswit= ch1 > - this was where we saw this issue). We were using VLANs and bridging across VLANs, this may have compounded our problem. We we put openvpn on it to connect two datacenters, we got similar broadcasts storms over the VPN connection as well. I was going to do something similar to connect family networks using openvpn at home until we ran into the problem. I think disbanded the project, maybe I'll have to look into it again if VLANs were the problem. Robert LeBlanc Life Sciences & Undergraduate Education Computer Support Brigham Young University