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: "Kirk Allan" <kallan@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] peth0 received packet on own address
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Sat, 29 Apr 2006 17:44:03 +0100
Delivery-date: Sat, 29 Apr 2006 09:44:30 -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: AcZrBCC1lfUXoLXiRXy1n3H8guFHEwAp4Mig
Thread-topic: [Xen-devel] peth0 received packet on own address
> I've been looking into an issue were in the message file I see: 
> Apr 28 11:43:10 kdell kernel: peth0: received packet with  
> own address as source address
> Trying to match the time stamp in the message file to a 
> packet trace captured by ethereal, I found that the offending 
> packets are of the type
> ICMPv6 Multicast Listener Report Message v2, ICMPv6 Neighbor 
> Solicitation, or ICMPv6 Router Solicitation packets.  It 
> looks like these packets are sent every time a network 
> interface is brought up.  In this case it is when peth0 is 
> brought up from the network-bridge script since the MAC 
> address is fe:ff:ff:ff:ff:ff.  When a peth0 comes up, all 
> other machines with a peth0 up and running will receive the 
> packets and log the messages.
> Is this an issue of concern?  

It's not of particular concern, but it would be nice to make them stop.

Is it the 'ip link set dev X up' line that causes the packet to be sent?
Does anyone know how to make them stop?


Xen-devel mailing list