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


RE: [Xen-devel] peth0 received packet on own address

To: "Nivedita Singhvi" <niv@xxxxxxxxxx>
Subject: RE: [Xen-devel] peth0 received packet on own address
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Sun, 30 Apr 2006 09:34:53 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Kirk Allan <kallan@xxxxxxxxxx>
Delivery-date: Sun, 30 Apr 2006 01:35:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZrtuHtoazETo7pRaKyYuZZ3P/O9gAeb8Dw
Thread-topic: [Xen-devel] peth0 received packet on own address
> We shouldn't be doing all of those things (peth0) on the 
> guest OSs - we had gone to some pains to make sure the MAC 
> was unique across the system - have we regressed in that due 
> to the -xen kernel or some other reason?

It's the internal vifX.X interfaces that have the fe:ff:... addresses.
There really is no business for any of these interfaces to be sourcing
packets at all.

Is there an option to the 'ip' tool when bringing the interface up to
prevent the ipv6 router solicitation?

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>