From: Andrew Theurer <habanero@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: networking oddities, present status ? changeset: 7145:71466686d026
Date: Fri, 30 Sep 2005 17:32:22 -0500 [thread overview]
Message-ID: <433DBCF6.1050106@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E0B4@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>>I have been experiencing some oddities as well. Xen/bridge
>>networking works on some switches, but not on others. Also
>>if I have one host with a domU communicating to another host,
>>an unrelated host (with xen) will sometimes get "peth0:
>>received packet with own address as source address" error
>>messages. I have to wonder if all these bridges on the xen
>>equipped hosts need unique MAC addresses (they all have
>>fe:ff:ff:ff:ff:ff)
>>
>>
>
>Interesting. Perhaps run a "tcpdump ether host fe:ff:ff:ff:ff:ff" and
>see if any other host is sending packets with that as a src address. I
>wander if one of the hosts on the network has STP turned on?
>
>
I give that a shot. I have a feeling at least one of the three switches
I have in my network may have STP on, and I guess I should check the xen
hosts as well (they really should all be using the same network-bridge
script). If STP is off everywhere, is there any reason to not use
fe:ff:ff:ff:ff:ff on all xen-br0 devices?
-Andrew
next prev parent reply other threads:[~2005-09-30 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 21:19 networking oddities, present status ? changeset: 7145:71466686d026 Ian Pratt
2005-09-30 22:32 ` Andrew Theurer [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-01 10:17 Ian Pratt
2005-10-11 15:02 ` Andrew Theurer
2005-09-30 18:10 Ted Kaczmarek
2005-09-30 20:02 ` Andrew Theurer
2005-09-30 20:50 ` Nivedita Singhvi
2005-09-30 21:16 ` Ted Kaczmarek
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=433DBCF6.1050106@us.ibm.com \
--to=habanero@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.