From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Kaczmarek Subject: Re: networking oddities, present status ? changeset: 7145:71466686d026 Date: Fri, 30 Sep 2005 17:16:28 -0400 Message-ID: <1128114988.3668.164.camel@pluto.linsolutions.com> References: <1128103806.3668.146.camel@pluto.linsolutions.com> <200509301502.50666.habanero@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7BIT Return-path: In-reply-to: <200509301502.50666.habanero@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: habanero@us.ibm.com Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > . > > 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