From: Oliver Mangold <o.mangold@gmail.com>
To: netdev@vger.kernel.org
Subject: enable/disable temporary IPv6 per prefix
Date: Sun, 11 Sep 2016 09:29:16 +0200 [thread overview]
Message-ID: <74afa986-01e5-729e-8847-2181f576893f@gmail.com> (raw)
Hi,
I have a question as a relatively new user to IPv6. I am wondering if it
is currently possible to enable/disable the usage of temporary addresses
on a per-prefix basis. My current understanding is that the feature is
enabled by the the 'use_tempaddr' sysctl attribute, which is
per-interface. What I would like to do is disable temp addresses for ULA
prefixes. Did I miss something and this can already be done, or is it a
feature planned for the future, maybe? RFC4941 seems to agree that this
is a valid use case:
Additionally, sites might wish to selectively enable or disable the use
of temporary addresses for some prefixes. For example, a site might
wish to disable temporary address generation for "Unique local" [ULA]
prefixes while still generating temporary addresses for all other global
prefixes. Another site might wish to enable temporary address
generation only for the prefixes 2001::/16 and 2002::/16, while
disabling it for all other prefixes. To support this behavior,
implementations SHOULD provide a way to enable and disable generation of
temporary addresses for specific prefix subranges. This per-prefix
setting SHOULD override the global settings on the node with respect to
the specified prefix subranges. Note that the pre-prefix setting can be
applied at any granularity, and not necessarily on a per-subnet basis.
Best regards,
Oliver
next reply other threads:[~2016-09-11 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 7:29 Oliver Mangold [this message]
2016-09-12 15:15 ` enable/disable temporary IPv6 per prefix Hannes Frederic Sowa
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=74afa986-01e5-729e-8847-2181f576893f@gmail.com \
--to=o.mangold@gmail.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).