From: Nivedita Singhvi <niv@us.ibm.com>
To: Ted Kaczmarek <tedkaz@optonline.net>
Cc: xen-devel@lists.xensource.com, Ewan Mellor <ewan@xensource.com>
Subject: Re: network-bridge script reworked
Date: Wed, 19 Oct 2005 16:45:30 -0700 [thread overview]
Message-ID: <4356DA9A.2040101@us.ibm.com> (raw)
In-Reply-To: <1129762773.30682.23.camel@pluto.linsolutions.com>
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
next prev parent reply other threads:[~2005-10-19 23:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 21:44 network-bridge script reworked Ian Pratt
2005-10-19 22:00 ` Ted Kaczmarek
2005-10-19 22:10 ` Nivedita Singhvi
2005-10-19 22:40 ` Ewan Mellor
2005-10-19 22:59 ` Ted Kaczmarek
2005-10-19 23:45 ` Nivedita Singhvi [this message]
2005-10-20 11:00 ` Ted Kaczmarek
-- strict thread matches above, loose matches on Subject: below --
2005-10-19 9:35 Kurt Garloff
2005-10-19 10:58 ` Ewan Mellor
2005-10-19 11:15 ` Charles Duffy
2005-10-20 10:41 ` Ewan Mellor
2005-10-20 18:22 ` Kurt Garloff
2005-10-21 13:48 ` Ewan Mellor
2005-10-21 14:44 ` Kurt Garloff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4356DA9A.2040101@us.ibm.com \
--to=niv@us.ibm.com \
--cc=ewan@xensource.com \
--cc=tedkaz@optonline.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.