headers
martin f krafft | 4 Dec 14:24
Favicon

Bug#507788: sysctl.conf read before ipv6 module loaded, so cannot set ipv6 settings

Package: procps
Version: 1:3.2.7-9
Severity: serious
Tags: ipv6
File: /etc/sysctl.conf

Setting kernel variables (/etc/sysctl.conf)...error:
"net.ipv6.conf.default.autoconf" is an unknown key
error: "net.ipv6.conf.default.accept_ra" is an unknown key
error: "net.ipv6.conf.default.accept_ra_defrtr" is an unknown key
error: "net.ipv6.conf.default.accept_ra_pinfo" is an unknown key
error: "net.ipv6.conf.default.accept_source_route" is an unknown key
error: "net.ipv6.conf.default.accept_redirects" is an unknown key
error: "net.ipv6.conf.default.forwarding" is an unknown key
error: "net.ipv6.conf.all.autoconf" is an unknown key
error: "net.ipv6.conf.all.accept_ra" is an unknown key
error: "net.ipv6.conf.all.accept_ra_defrtr" is an unknown key
error: "net.ipv6.conf.all.accept_ra_pinfo" is an unknown key
error: "net.ipv6.conf.all.accept_source_route" is an unknown key
error: "net.ipv6.conf.all.accept_redirects" is an unknown key
error: "net.ipv6.conf.all.forwarding" is an unknown key
failed.
Mounting local filesystems...done.
Activating swapfile swap...done.
Setting up resolvconf...done.
Setting up networking....

The ipv6 module on Debian is loaded only by the networking code, so
either sysctl.conf should run after that, or the ipv6 module needs
to be loaded before somehow.
(Continue reading)

Permalink | Reply |
headers
Craig Small | 5 Dec 12:11
Favicon

Bug#507788: sysctl.conf read before ipv6 module loaded, so cannot set ipv6 settings

On Thu, Dec 04, 2008 at 02:26:54PM +0100, martin f krafft wrote:
> The ipv6 module on Debian is loaded only by the networking code, so
> either sysctl.conf should run after that, or the ipv6 module needs
> to be loaded before somehow.
There is no sensible fix for this.  The problem is that any time is the
wrong time for the init script to run, for someone.

If I shift it back, other stuff won't work. The ipv6 stuff is commented
out, for some reason I don't get this problem you experience. In any
case if there is no fix for it I'm going to downgrade the bug.

 - Craig

--

-- 
Craig Small      GnuPG:1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
http://www.enc.com.au/                             csmall at : enc.com.au
http://www.debian.org/          Debian GNU/Linux, software should be Free
Permalink | Reply |
headers
martin f krafft | 5 Dec 12:29
Favicon

Bug#507788: sysctl.conf read before ipv6 module loaded, so cannot set ipv6 settings

also sprach Craig Small <csmall <at> debian.org> [2008.12.05.1211 +0100]:
> There is no sensible fix for this.  The problem is that any time is the
> wrong time for the init script to run, for someone.

Do you have specific examples that would break if procps ran at S40?

--

-- 
 .''`.   martin f. krafft <madduck <at> debian.org>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems
Permalink | Reply |
headers
Craig Small | 5 Dec 12:35
Favicon

Bug#507788: sysctl.conf read before ipv6 module loaded, so cannot set ipv6 settings

On Fri, Dec 05, 2008 at 12:29:43PM +0100, martin f krafft wrote:
> also sprach Craig Small <csmall <at> debian.org> [2008.12.05.1211 +0100]:
> > There is no sensible fix for this.  The problem is that any time is the
> > wrong time for the init script to run, for someone.
> Do you have specific examples that would break if procps ran at S40?
Shifting it to 40 would probably fix your ipv6 related bug, I guess.

There are some settings that need to be set before the interfaces come
online, I'm not sure of the specifics but I do know these keys are out
there and they do need to be set before networking starts.

Ideally there probably should be some sort of runlevel type sysctl
setup, that's going to be fiddly and not trivial to write, but not
impossible either.

My worry is that we move it, you're happy, people who have similiar
problems to you are happy but then suddenly another group of people
spring up with "hey, why did you move sysctl, you broke my system now"

 - Craig
--

-- 
Craig Small      GnuPG:1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
http://www.enc.com.au/                             csmall at : enc.com.au
http://www.debian.org/          Debian GNU/Linux, software should be Free
Permalink | Reply |
headers
Didier Raboud | 5 Dec 13:42
Gravatar

Bug#507788: sysctl.conf read before ipv6 module loaded, so cannot set ipv6 settings

Le vendredi 5 décembre 2008 12:35:44 Craig Small, vous avez écrit :
> On Fri, Dec 05, 2008 at 12:29:43PM +0100, martin f krafft wrote:
> > also sprach Craig Small <csmall <at> debian.org> [2008.12.05.1211 +0100]:
> > > There is no sensible fix for this.  The problem is that any time is the
> > > wrong time for the init script to run, for someone.
> >
> > Do you have specific examples that would break if procps ran at S40?
>
> Shifting it to 40 would probably fix your ipv6 related bug, I guess.
>
> There are some settings that need to be set before the interfaces come
> online, I'm not sure of the specifics but I do know these keys are out
> there and they do need to be set before networking starts.
>
> Ideally there probably should be some sort of runlevel type sysctl
> setup, that's going to be fiddly and not trivial to write, but not
> impossible either.
>
> My worry is that we move it, you're happy, people who have similiar
> problems to you are happy but then suddenly another group of people
> spring up with "hey, why did you move sysctl, you broke my system now"
>
>  - Craig

As ipv6 is a release goal, my guess is that a solution has to be found.
Then, why not getting opininons by consulting -devel about

* what would happen if procps was moved 
from	S30
		Required-Start:    mountkernfs
(Continue reading)

Permalink | Reply |
headers
martin f krafft | 7 Dec 11:52
Favicon

Bug#507788: sysctl.conf read before ipv6 module loaded, so cannot set ipv6 settings

also sprach Didier Raboud <didier <at> raboud.com> [2008.12.05.1342 +0100]:
> As ipv6 is a release goal, my guess is that a solution has to be found.

Maybe the easiest solution is simply to load the ipv6 module early
on, unconditionally?

--

-- 
 .''`.   martin f. krafft <madduck <at> d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems

warning at the gates of bill:
abandon hope, all ye who press <enter> here...
Permalink | Reply |
headers
Craig Small | 7 Dec 22:25
Favicon

Bug#507788: sysctl.conf read before ipv6 module loaded, so cannot set ipv6 settings

On Fri, Dec 05, 2008 at 01:42:50PM +0100, Didier Raboud wrote:
> As ipv6 is a release goal, my guess is that a solution has to be found.
> Then, why not getting opininons by consulting -devel about
It will break things, not might, it will. The easiest examples being
anything that uses the /conf/default/ in the network setup and not
/conf/all/ and anything that needs to be there before the interfaces 
are brought online.

There will be a small but definite gap between when an interface is
brought up and when the parameters are applied. Some of those parameters
are security related and so there is a problem right there.

While IPv6 is a release goal, having sysctl handle the fact the module
is not there first is not. There are ways to have the ipv6 module load
late and to have kernel parameters setup in it.

 - Craig
--

-- 
Craig Small      GnuPG:1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
http://www.enc.com.au/                             csmall at : enc.com.au
http://www.debian.org/          Debian GNU/Linux, software should be Free
Permalink | Reply |

Gmane