All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel@lists.xensource.com, Kirk Allan <kallan@novell.com>
Subject: Re: peth0 received packet on own address
Date: Sat, 29 Apr 2006 16:41:49 -0700	[thread overview]
Message-ID: <4453F9BD.903@us.ibm.com> (raw)
In-Reply-To: <4453A9BE.5000702@us.ibm.com>

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

  reply	other threads:[~2006-04-29 23:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-29 16:44 peth0 received packet on own address Ian Pratt
2006-04-29 18:00 ` Nivedita Singhvi
2006-04-29 23:41   ` Nivedita Singhvi [this message]
2006-05-01 14:53 ` Kirk Allan
  -- strict thread matches above, loose matches on Subject: below --
2006-05-01 15:28 Ian Pratt
2006-04-30  8:34 Ian Pratt
2006-05-01 15:26 ` Nivedita Singhvi
2006-04-28 20:40 Kirk Allan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4453F9BD.903@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=kallan@novell.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.