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

Bug#604948: marked as done (IPv6 problems in Squeeze)

Your message dated Thu, 25 Nov 2010 17:53:25 +0000
with message-id <1290707605.3214.2.camel@localhost>
and subject line Re: Bug#604948: IPv6 problems in Squeeze
has caused the Debian Bug report #604948,
regarding IPv6 problems in Squeeze
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
604948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604948
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.32-5-amd64
Version: 2.6.32-27

With ipv6 buildt into kernel and not available as a kernel module, there
is no way to pass on the module options that those of us who run IPv6 in
production environments very often need.

For example, I have servers that need to explicitly have IPv6 configured
staticly, that sit on LANs that have autoconf/ra enabled.

On debian this should mean having ipv6 in /etc/modules, and for example in
/etc/modprobe.d/ipv6.conf have "ipv6 options disable_ipv6=1 autoconf=0"
and also a whole range of entries in for example /etc/sysctl.d/ipv6.conf:

net.ipv6.conf.default.autoconf=0
net.ipv6.conf.default.accept_ra=0
net.ipv6.conf.default.disable_ipv6 = 0
net.ipv6.conf.all.autoconf=0
net.ipv6.conf.all.accept_ra=0
net.ipv6.conf.lo.disable_ipv6=0
net.ipv6.conf.eth0.disable_ipv6=0

(these are marvels of the 2.6.31 kernel or thereabouts.)

and then lastly, one do ofcourse need entries in /etc/network/interfaces.


Now - it would ofcourse be _very much_ prefared that if one in
/etc/network/interfaces configure interfaces with static ipv6 addresses
and static router, all of the above happen automatically. A workaround
that we've been using till now is to have in interfaces for example:

auto eth0
   iface eth0 inet static
      address 10.10.10.10
      gateway 10.10.10.1
      netmask 255.255.255.0
   iface eth0 inet6 static
      address 2001:700:0::beaf
      gateway 2001:700::1
      netmask 64
   up /sbin/sysctl -w net.ipv6.conf.eth0.autoconf=0
   up /sbin/sysctl -w net.ipv6.conf.eth0.accept_ra=0

But this only work _most_ of the time. Every now and then the sysctl lines are
not performed quickly enough and due to bad luck the server also picks up
autoconf address and router announcement, ending up with double set of
addresses and non-static default route.

So I beg you - let ipv6 continue to exist as module and not be buildt into kernel.

-- 
Kolbjørn Barmen
UNINETT Driftsenter

--- End Message ---
--- Begin Message --- 
On Thu, 2010-11-25 at 18:24 +0100, Kolbjørn Barmen wrote: 
> Package: linux-image-2.6.32-5-amd64
> Version: 2.6.32-27
> 
> With ipv6 buildt into kernel and not available as a kernel module, there
> is no way to pass on the module options that those of us who run IPv6 in
> production environments very often need.

You can set them as kernel parameters, adding the prefix 'ipv6.' (in
fact this works for most code that can be either modular or built-in,
using the module name and '.' as prefix).

[...]
> So I beg you - let ipv6 continue to exist as module and not be buildt
> into kernel.

No, this would be almost as silly as making IPv4 a module (which is not
actually supported).

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: