[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Kirk Allan" <kallan@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • 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?

Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.