This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Re: Bug 339 - peth1: received packet with own address as sou

To: "John Hannfield" <hal9020@xxxxxxxxx>
Subject: [Xen-users] Re: Bug 339 - peth1: received packet with own address as source address
From: "Cyrus Katrak" <katrakcr@xxxxxxxxxxxx>
Date: Fri, 4 May 2007 10:43:43 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 May 2007 10:15:11 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=IIyGqqhX9go5t3SE7hiTxf/AX5M0lxIhXYvSQ3BETGxloFuAOiEKV8DBLj7OhprmyjQCJ9gl+JW3ZaOVXc7NtaBINclhyi/9uAatwKB4+z5mUYwmSz6CQSW2gqNxkHLmGT57H56+OcHDSZMcg6skk7ghNMHUbOgpcvGxKcb1kqQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=TBMRe/lpiM2kZKMZ+fqnclOPCk0JBIwakQgMT5MeIxluoRTgtD0zpeDw5tZc6SurW76tPMsusjkT1gqNCPG05t4dw8AK5vyiXvrokTN6aBPDhJsbnr2AFbzBQqMeEftBoa7/7bt3u9KFL8bwj6/R6nKMtT5J7XWJ0+ydGHWaRdY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4d95b0990705040400p1d63c22bmbcefa6f6a23924ca@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4d95b0990705040400p1d63c22bmbcefa6f6a23924ca@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
After implementing the patch, you must edit the line that says:
on ONE of the dom0's.
on Your first dom0 use: macid="F0"
on your second dom0 use: macid="F1"

You mentioned the possiblity of an unkown dom0 on the network. I
believe you can use any MAC you want, but changing macid="F0" to some
other 2-hex digit ID should provide you with enough options.

Please let me know if this works

On 5/4/07, John Hannfield <hal9020@xxxxxxxxx> wrote:

I have two xen servers on the same subnet, and I'm seeing these messages
logged every minute to /var/log/messages

peth1: received packet with own address as source address

It's in bugzilla as bug 339

It seems to be due to both machines using the same hardware address
for dom0 peth1.  So I have implemented the patch by  Cyrus Katrak
and changed one machine to


However it still occurs. There could be a (unkown to me) dom0 server
on the network with this MAC address, so my question is:
Can I just assign any MAC address I want to  peth1 ?
Like one of the private range that I use for my guests?
Or does it have to be FE:FF:FF:FF:xx:xx ?



Xen-users mailing list