I think this should be reopened (or another bug opened, I don't know). I can't
put an ipv6 settings in /etc/sysctl.conf (eg. net/ipv6/conf/all/use_tempaddr =
2 and net/ipv6/conf/default/use_tempaddr = 2) because ipv6 isn't loaded early
enough.
My workaround is to put ipv6 in /etc/modules.
** Changed in: Ubuntu
Status: Fix Committed = Fix Released
--
IPv6 module is not loaded early enough
https://launchpad.net/bugs/7091
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: Ubuntu
Status: Needs Info = In Progress
--
IPv6 module is not loaded early enough
https://launchpad.net/bugs/7091
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Fixed in feisty by modprobing ipv6 when inet6 family is requested on one
interface.
** Changed in: Ubuntu
Status: In Progress = Fix Committed
--
IPv6 module is not loaded early enough
https://launchpad.net/bugs/7091
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Not fixed in Edgy, not fixed in Feisty.
It is also a concern because you can't switch autoconf off until the
module is loaded, so you kind of need it before sysctl.conf is read
(unless you want ugly pre-up and up hacks).
--
IPv6 module is not loaded early enough
https://launchpad.net/bugs/7091
Can you please give us the current status of the bug? Is it fixed in
Edgy/ Feisty?
** Changed in: Ubuntu
Status: Confirmed = Needs Info
--
IPv6 module is not loaded early enough
https://launchpad.net/bugs/7091
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Ping for edgy
--
IPv6 module is not loaded early enough
https://launchpad.net/bugs/7091
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Tags added: ipv6
--
IPv6 module is not loaded early enough
https://launchpad.net/bugs/7091
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
