All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralph Passgang <xen@debianbase.de>
To: xen-devel@lists.xensource.com
Subject: Re: ipv6 addresses on vifX.Y interfaces and bridges
Date: Mon, 7 Jan 2008 02:10:06 +0100	[thread overview]
Message-ID: <200801070210.06593.xen@debianbase.de> (raw)
In-Reply-To: <20080106224813.GE5345@redhat.com>

Am Sonntag, 6. Januar 2008 23:48:13 schrieb Daniel P. Berrange:
> On Mon, Jan 07, 2008 at 09:44:09AM +1100, James Harper wrote:
> > > On Mon, Jan 07, 2008 at 09:26:43AM +1100, James Harper wrote:
> > > > The network scripts appear to set noarp on all the vifX.Y and
> >
> > xen-brX
> >
> > > > interfaces, but I also need to remove the IPv6 address and stop the
> > > > interfaces participating in autoconfiguration...
> > > >
> > > > Has anyone done this already?
> > >
> > > You don't need to remove the link-local IPv6 addresses, they are
> >
> > harmless.
> >
> > > The key is to stop auto-conf taking place on the bridge. The way todo
> > > this is to set the mtu of the bridge to something tiny (eg 68) before
> > > bringing the interface up, and then once it is up, restore the mtu to
> > > its normal 1500.
> > >
> > > This was previously merged in xen-unstable, in 13364
> >
> > That sounds a bit kludgy... wouldn't it be better to make use of
> > /proc/sys/net/ipv6/<interface>/autoconf and/or .../accept_ra?
>
> Would have to ask Herbert about that - when he wrote the patch this was
> the only reliable way of selectively disabling Ipv6 on the bridge, but
> not other eth devices.
>
> > Wouldn't the bridge just autoconf next time an ra is sent once its mtu
> > is back up to 1500?
>
> No, because the low MTU means it never gets assigned a link-local address
> and thus has no way to parcitipate in ipv6 autoconf thereafter.

But it's a dirty hack, isn't it?
what about just using the ip tool to get rid of the ipv6 address after the 
interface has been configured?

"ip -6 addr flush dev ethX" (or whatever device) should do the trick... :)

it removes any global or local address on the interface and prevents any 
further autoconfiguration.

> Dan.

  reply	other threads:[~2008-01-07  1:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06 22:26 ipv6 addresses on vifX.Y interfaces and bridges James Harper
2008-01-06 22:36 ` Daniel P. Berrange
2008-01-06 22:44   ` James Harper
2008-01-06 22:48     ` Daniel P. Berrange
2008-01-07  1:10       ` Ralph Passgang [this message]
2008-01-08  7:45         ` RelocationProtocol? tgh

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=200801070210.06593.xen@debianbase.de \
    --to=xen@debianbase.de \
    --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.