All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: ipv6 addresses on vifX.Y interfaces and bridges
Date: Sun, 6 Jan 2008 22:36:41 +0000	[thread overview]
Message-ID: <20080106223641.GB5345@redhat.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0131A647@trantor>

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

diff -r c71fe03f086f -r c2fd75d7e2b7 tools/examples/xen-network-common.sh
--- a/tools/examples/xen-network-common.sh      Fri Jan 12 15:19:23 2007 +0000
+++ b/tools/examples/xen-network-common.sh      Fri Jan 12 15:23:07 2007 +0000
@@ -117,7 +117,12 @@ create_bridge () {
         ip link set ${bridge} arp off
         ip link set ${bridge} multicast off
     fi
+
+    # A small MTU disables IPv6 (and therefore IPv6 addrconf).
+    mtu=$(ip link show ${bridge} | sed -n 's/.* mtu \([0-9]\+\).*/\1/p')
+    ip link set ${bridge} mtu 68
     ip link set ${bridge} up
+    ip link set ${bridge} mtu ${mtu:-1500}
 }
 
 # Usage: add_to_bridge bridge dev


But for some reason got chopped out in changeset 15203

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2008-01-06 22:36 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 [this message]
2008-01-06 22:44   ` James Harper
2008-01-06 22:48     ` Daniel P. Berrange
2008-01-07  1:10       ` Ralph Passgang
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=20080106223641.GB5345@redhat.com \
    --to=berrange@redhat.com \
    --cc=james.harper@bendigoit.com.au \
    --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.