From: Brian Haley <brian.haley@hp.com>
To: "Kolbjørn Barmen" <linux@kolla.no>
Cc: David Miller <davem@davemloft.net>,
yoshfuji@st-paulia.net, netdev@vger.kernel.org,
yoshfuji@linux-ipv6.org
Subject: Re: PROBLEM: IPv6 autoconf/accept_ra default values
Date: Tue, 24 Mar 2009 21:49:31 -0400 [thread overview]
Message-ID: <49C98DAB.5070100@hp.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0903202217590.4741@firda.kolla.no>
Kolbjørn Barmen wrote:
>> Are the two parameters he described for this going to be good enough for
>> you? I was thinking of also adding a "default" keyword to control
>> net.ipv6.conf.default.*, for example:
>>
>> disable_ipv6=all,default,eth0,eth1
>> autoconf=all,default,eth2,eth3
>>
>> This is because "default" is what's inherited by all the ethX values,
>> "all" is the big hammer.
>
> This is still unclear for me. I've been assuming that by changing
> "default" all future devices will inherit the value, but leaving existing
> devices as is. "all" I've assumed takes all existing interfaces, but
> leaving default as is. Is this what you are saying?
"default" is what's inherited by future devices, "all" is supposed to be the
over-ride for all devices, but doesn't change any device-specific values.
>> Of course I could be over-thinking this and the simple solution could work just
>> fine:
>>
>> disable_ipv6=1
>> autoconf=0
>>
>> Then just let you put things in sysctl.conf to enable what you want. I'll play
>> with that first to see if it's enough.
>
> I think this would be enough yes. Probably best to think about how one
> would be able to set boot paramets so that a machine gets static address
> and no autoconf, for example for NFS-root etc. This falls under same
> "mission"?
My patch wouldn't address getting a static address via a module parameter, that
can still be done in, for example, /etc/network/interfaces. So no, this isn't
part of my "mission", just getting the basic functionality in place.
>>> How about the behaviour that I described:
>>>
>>> root:~# sysctl net.ipv6.conf.all.accept_ra
>>> net.ipv6.conf.all.accept_ra = 1
>>> root:~# sysctl -w net.ipv6.conf.all.accept_ra=0
>>> net.ipv6.conf.all.accept_ra = 0
>>> root:~# sysctl net.ipv6.conf.eth0.accept_ra
>>> net.ipv6.conf.all.accept_ra = 1
>>>
>>> Is this intended behaviour or not? Bug or (mis)feature?
>> I *think* that's intended, at least it's one of the ways IPv6 differs from IPv4
>> - setting "all" doesn't reset to individual nic settings. But the code in
>> ndisc_router_discovery() should probably check the "all" flag and drop the RA.
>> The other "all" sysctl's should behave the same, so someone needs to take a
>> deeper look.
>
> OK, I have this weird feeling that this "worked" some years ago, but I
> dont have any old systems to try out that theory on. I fail to see wht
> purpose "all" has, if it isn't setting the value of all interfaces.
I fixed the autoconf one, but this would still need to be addressed in a future
patch, trying to sneak-in before the deadline. Might be too late...
I sent the actual patch to netdev a few minutes ago for review.
-Brian
next prev parent reply other threads:[~2009-03-25 1:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 9:50 PROBLEM: IPv6 autoconf/accept_ra default values Kolbjørn Barmen
2009-03-18 1:06 ` Kolbjørn Barmen
2009-03-18 3:33 ` YOSHIFUJI Hideaki
2009-03-20 6:44 ` David Miller
2009-03-20 8:48 ` Kolbjørn Barmen
2009-03-20 18:02 ` Brian Haley
2009-03-20 21:50 ` Kolbjørn Barmen
2009-03-25 1:49 ` Brian Haley [this message]
[not found] <alpine.LNX.2.00.0902231319380.14151@halbrend.uninett.no>
2009-02-23 23:46 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49C98DAB.5070100@hp.com \
--to=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=linux@kolla.no \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
--cc=yoshfuji@st-paulia.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).