All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kirk Allan" <kallan@novell.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: RE: peth0 received packet on own address
Date: Mon, 01 May 2006 08:53:43 -0600	[thread overview]
Message-ID: <4455CC97.39DB.0076.0@novell.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4BA4EC@liverpoolst.ad.cl.cam.ac.uk>

>>  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?

Yes, it is the 'ip link set ${pdev} up' line.

> Does anyone know how to make them stop?
> 
> Thanks,
> Ian

  parent reply	other threads:[~2006-05-01 14:53 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
2006-05-01 14:53 ` Kirk Allan [this message]
  -- 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=4455CC97.39DB.0076.0@novell.com \
    --to=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.