All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Kirk Allan <kallan@novell.com>
Subject: Re: peth0 received packet on own address
Date: Mon, 01 May 2006 08:26:14 -0700	[thread overview]
Message-ID: <44562896.9050608@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4BA4F3@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:
>>We shouldn't be doing all of those things (peth0) on the 
>>guest OSs - we had gone to some pains to make sure the MAC 
>>was unique across the system - have we regressed in that due 
>>to the -xen kernel or some other reason?
> 
> 
> It's the internal vifX.X interfaces that have the fe:ff:... addresses.
> There really is no business for any of these interfaces to be sourcing
> packets at all.
> 
> Is there an option to the 'ip' tool when bringing the interface up to
> prevent the ipv6 router solicitation?

The ip tool mostly configures the settings on the
card, and most of these are network protocol functions
which merely get initiated once the interface comes
up - they are mostly controlled by sysctl kernel
parameters. So, for instance, setting

/proc/sys/net/ipv6/conf/$interface/autoconf = 0

will turn off most of that. However, the /proc
entry for the device is only created when we
register the device, and the MLD and routing
functions get initiated only when we designate
the interface state as UP.  Somewhere in between
performing those two steps, we should turn off
those sysctl vars.

Will test that today..

thanks,
Nivedita

  reply	other threads:[~2006-05-01 15:26 UTC|newest]

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