Kolbjørn Barmen <kolbjorn.bar...@uninett.no> writes:
> 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 have exactly the same possibilities as before. Quoting from
Documentation/kernel-parameters.txt:
<quote>
Module parameters for modules that are built into the kernel image
are specified on the kernel command line with the module name plus
'.' plus parameter name, with '=' and value if appropriate, such as:
usbcore.blinkenlights=1
</quote>
A "disable" option has also been added for completely disabling the
module, for those who wanted to blacklist it (which I guess you don't
want, but still...)
> For example, I have servers that need to explicitly have IPv6 configured
> staticly, that sit on LANs that have autoconf/ra enabled.
> 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.
I don't think that's necessarily something everyone would want. I can
imagine situations where you'd like both a static address and a SLAAC
address on an interface.
> 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.
How about using pre-up? Wouldn't that always work?
Bjørn
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87r5e92rxa....@nemi.mork.no
