From: Adam Osuchowski <adwol@zonk.pl>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 11655] New: /proc/sys/net/ipv6/conf/all/* controls don't work
Date: Mon, 13 Oct 2008 12:13:34 +0200 [thread overview]
Message-ID: <20081013101334.6b8b4567@zonk.pl> (raw)
In-Reply-To: <20081013.003239.89070363.davem@davemloft.net>
David Miller wrote:
> Not a bug.
>
> These "global" setting have to be set to the desired value before the
> device is created. And it is at creation time that these global
> values are "inherited" by the device.
>
> Afterwards changes to the global value will not propagate to those
> devices again, because that might override a changed setting made
> by the user.
>
> It is only newly created devices which get these values.
I understand you are talking about /proc/sys/net/ipv6/conf/default/*
controls. If so, it's ok, but I talked about /proc/sys/net/ipv6/conf/all/*
controls. Documentation/networking/ip-sysctl.txt says:
conf/default/*:
Change the interface-specific default settings.
conf/all/*:
Change all the interface-specific settings.
so what is the difference between default and all in the context of your
statement? In my opinion, it could be understood that default settings
are inherited and those from "all" directory change values for all
current devices.
next prev parent reply other threads:[~2008-10-13 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11655-10286@http.bugzilla.kernel.org/>
2008-10-03 6:18 ` [Bugme-new] [Bug 11655] New: /proc/sys/net/ipv6/conf/all/* controls don't work Andrew Morton
2008-10-13 7:32 ` David Miller
2008-10-13 10:13 ` Adam Osuchowski [this message]
2008-10-13 18:37 ` 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=20081013101334.6b8b4567@zonk.pl \
--to=adwol@zonk.pl \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--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).