From: Ted Kaczmarek <tedkaz@optonline.net>
To: habanero@us.ibm.com
Cc: xen-devel@lists.xensource.com
Subject: Re: networking oddities, present status ? changeset: 7145:71466686d026
Date: Fri, 30 Sep 2005 17:16:28 -0400 [thread overview]
Message-ID: <1128114988.3668.164.camel@pluto.linsolutions.com> (raw)
In-Reply-To: <200509301502.50666.habanero@us.ibm.com>
> .
>
> 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)
>
> -Andrew
Only the bridge that xend brings up automatically is getting that mac in
my setup. The other two bridges I have use the mac address of the
ethernet they are a slave to. I am using FC4 domO.
I would think the bridge should always grab the mac address of the
ethernet is is a slave too, the dom0 than gets treated just like any
other managed bridge device, clean and simple.
I suspect their may be a good reason for this, just beyond my scope of
knowledge.
Regards,
Ted
next prev parent reply other threads:[~2005-09-30 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 18:10 networking oddities, present status ? changeset: 7145:71466686d026 Ted Kaczmarek
2005-09-30 20:02 ` Andrew Theurer
2005-09-30 20:50 ` Nivedita Singhvi
2005-09-30 21:16 ` Ted Kaczmarek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-30 21:19 Ian Pratt
2005-09-30 22:32 ` Andrew Theurer
2005-10-01 10:17 Ian Pratt
2005-10-11 15:02 ` Andrew Theurer
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=1128114988.3668.164.camel@pluto.linsolutions.com \
--to=tedkaz@optonline.net \
--cc=habanero@us.ibm.com \
--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.