From: David Ahern <dsa@cumulusnetworks.com>
To: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>,
netdev@vger.kernel.org
Cc: hannes@stressinduktion.org
Subject: Re: [PATCH] net: ipv6: Make address flushing on ifdown optional
Date: Tue, 16 Feb 2016 20:45:58 -0700 [thread overview]
Message-ID: <56C3ECF6.9090103@cumulusnetworks.com> (raw)
In-Reply-To: <56C3D6A3.7030605@miraclelinux.com>
On 2/16/16 7:10 PM, YOSHIFUJI Hideaki wrote:
> Hi,
>
> David Ahern wrote:
>> On 2/16/16 1:45 AM, YOSHIFUJI Hideaki wrote:
>>>> diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
>>>> index 24ce97f42d35..7ddbbb67f0db 100644
>>>> --- a/Documentation/networking/ip-sysctl.txt
>>>> +++ b/Documentation/networking/ip-sysctl.txt
>>>> @@ -1563,6 +1563,12 @@ temp_prefered_lft - INTEGER
>>>> Preferred lifetime (in seconds) for temporary addresses.
>>>> Default: 86400 (1 day)
>>>>
>>>> +keep_addr_on_down - BOOLEAN
>>>> + Keep all IPv6 addresses on an interface down event. If set static
>>>> + global addresses with no expiration time are not flushed.
>>>> +
>>>> + Default: disabled
>>>> +
>>>
>>> How about this:
>>> 1: enabled
>>> 0: system default
>>> -1: disabled
>>> so that an iterface can override system-wide config?
>>
>> It is my understanding that the 'all' settings override the individual
>> interface settings. From Documentation/networking/ip-sysctl.txt +1346:
>>
>> conf/all/*:
>> Change all the interface-specific settings.
>
> Well, document is not correct.
> 1) Some of "all" variables set all interface specific settings.
> 2) Some of "all" variables override interface specific settings.
> 3) Some provide "fall-back" values; such an interface specific
> setting overrides the corresponding "all" variable.
> (Note: "default" variables are values per-interface settings
> are initialized to.)
> 4) Others are ignored (the exists but no-ops).
Seems like a nightmare for an admin to understand which ones fall into
which category.
I really don't have a preference here beyond having the feature and
making it easy to enable (e.g., enable 'all' and it works for all). If
you want the 1/0/-1 trio and allow individual netdev settings to
override all then I will update the patch.
Thanks,
David
next prev parent reply other threads:[~2016-02-17 3:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 22:23 [PATCH] net: ipv6: Make address flushing on ifdown optional David Ahern
2016-02-13 22:25 ` David Ahern
2016-02-16 8:45 ` YOSHIFUJI Hideaki
2016-02-16 15:16 ` David Ahern
2016-02-17 2:10 ` YOSHIFUJI Hideaki
2016-02-17 3:45 ` David Ahern [this message]
2016-02-17 18:05 ` David Miller
2016-02-17 18:09 ` David Ahern
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=56C3ECF6.9090103@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=hannes@stressinduktion.org \
--cc=hideaki.yoshifuji@miraclelinux.com \
--cc=netdev@vger.kernel.org \
/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).