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: Mon, 1 May 2006 16:28:05 +0100
Delivery-date: Mon, 01 May 2006 08:28:22 -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: AcZtLxbGxCKqrj6zQF6yE4gIWGNuTAABCjuQ
Thread-topic: [Xen-devel] peth0 received packet on own 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.  

> > Is it the 'ip link set dev X up' line that causes the packet to be
> sent?
> Yes, it is the 'ip link set ${pdev} up' line.

Does anyone know if there's some parameter that can be given to the 'ip
link set' command to cause it not to send the ipv6 router solicitation?


Xen-devel mailing list

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