From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ted Kaczmarek <tedkaz@optonline.net>
Subject: Re: network-bridge script reworked
Date: Thu, 20 Oct 2005 07:00:22 -0400
Message-ID: <1129806022.30682.55.camel@pluto.linsolutions.com>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D32E4B8@liverpoolst.ad.cl.cam.ac.uk>
	<1129759215.30682.18.camel@pluto.linsolutions.com>
	<20051019224058.GA13970@leeni.uk.xensource.com>
	<1129762773.30682.23.camel@pluto.linsolutions.com>
	<4356DA9A.2040101@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7BIT
Return-path: <xen-devel-bounces@lists.xensource.com>
In-reply-to: <4356DA9A.2040101@us.ibm.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: xen-devel@lists.xensource.com, Ewan Mellor <ewan@xensource.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, 2005-10-19 at 16:45 -0700, Nivedita Singhvi wrote:
> Ted Kaczmarek wrote:
> 
> >>We have seen the old script get things into a state whereby the machine's
> >>routing tables claim to be going through peth0 rather than eth0.  At the very
> >>least, if this happened with two Xen machines on the network, then one would
> >>complain about packets coming from the other, and I have observed this behaviour
> >>directly.
> >>
> >>Can anyone claim to have seen the error message with only one Xen machine on
> >>the network?
> >>
> >>Ewan.
> > 
> > Nope, I have repeatedly tested and have only seen this when the
> > domU's/DomO's share a broadcast domain on the peth interface. Been
> > running test bed where eth0 is disconnected and xen-br0 is enslaved to
> > it for almost two days now. Not a single instance of this message.
> 
> Ted, are you saying only one machine, or was that multiple machines?
> Because we have not seen it with a single machine on the network (ok,
> would someone from the "big shop" correct me if they have?).
> 
> Jerone has been trying to recreate it right now and hasn't seen it
> so far.
> 
> I believe it is the scenario that Ewan describes above.
> 
> thanks,
> Nivedita

With 2 machines and dom0/U's  sharing a broadcast domain this problem
always occurs.


Ted