From: Tero Marttila <tero.marttila@aalto.fi>
To: <netdev@vger.kernel.org>
Subject: Behaviour of sysctl net.ipv6.conf.all.* parameters
Date: Wed, 24 Jun 2015 17:17:42 +0300 [thread overview]
Message-ID: <558ABC06.2060201@aalto.fi> (raw)
Hi,
I was exploring the behavior of various net.ipv6.conf.all parameters
such as use_tempaddr on Linux 3.16, but the behavior doesn't seem to
make sense.
The following settings do *not* result in privacy addresses on eth0:
net.ipv6.conf.all.use_tempaddr=2
net.ipv6.conf.eth0.use_tempaddr=0
But the following settings do:
net.ipv6.conf.all.use_tempaddr=0
net.ipv6.conf.eth0.use_tempaddr=2
This doesn't make sense per any of the AND/OR/MAX semantics as used for
e.g. net.ipv4.conf.all.
Looking at the net/ipv6/addrconf.c implementation, I can figure out
where net.ipv6.conf.default is implemented, and some handling for
specific devconf_all parameters (forwarding, disable_ipv6, proxy_ndp),
but I am unable to find any link between struct
netns_ipv6.devconf_all.use_tempaddr and struct inet6_dev.cnf.use_tempaddr.
Does anyone have any pointers for where this linking logic would be
implemented, or are the majority of net.ipv6.conf.all.* sysctl
parameters actually complete no-ops?
-- Tero Marttila
reply other threads:[~2015-06-24 14:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=558ABC06.2060201@aalto.fi \
--to=tero.marttila@aalto.fi \
--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).