From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nivedita Singhvi Subject: Re: peth0 received packet on own address Date: Sat, 29 Apr 2006 16:41:49 -0700 Message-ID: <4453F9BD.903@us.ibm.com> References: <4453A9BE.5000702@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4453A9BE.5000702@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Nivedita Singhvi Cc: Ian Pratt , xen-devel@lists.xensource.com, Kirk Allan List-Id: xen-devel@lists.xenproject.org Nivedita Singhvi wrote: > Ian Pratt wrote: > >>> 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 [snip] > Not compiling in support for MLDv2, etc in the kernel I should have also mentioned, although this is somewhat tangential to main issue - that if you are not using IPv6, and the default for your distro happens to be on, you might want to turn it off per interface by configuring it in the network interface configuration file.. This is distro-specific, but for example, in FC* you'd place a NETWORKING_IPV6=no in ifcfg-ethN, for instance. thanks, Nivedita