[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] ipv6 addresses on vifX.Y interfaces and bridges


  • To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Mon, 7 Jan 2008 09:44:09 +1100
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Sun, 06 Jan 2008 14:44:36 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AchQtKe/OqUuKrnkSnSmJsq2dmDODwAAKKbw
  • Thread-topic: [Xen-devel] ipv6 addresses on vifX.Y interfaces and bridges

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

Wouldn't the bridge just autoconf next time an ra is sent once its mtu
is back up to 1500?

Thanks

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.