From: David Ahern <dsahern@kernel.org>
To: Kyle Rose <krose@krose.org>
Cc: netdev@vger.kernel.org
Subject: Re: ULA and privacy addressing
Date: Sun, 28 Aug 2022 17:53:40 -0600 [thread overview]
Message-ID: <20220828235340.GA13078@u2004-local> (raw)
In-Reply-To: <CAJU8_nU2Yb1yR7j8zMEnF63Lszbu8MVbePWsuwG2_mimU9iwOg@mail.gmail.com>
On Thu, Aug 18, 2022 at 12:29:33PM -0400, Kyle Rose wrote:
> Does anyone have any opinions on the right way to implement a
> configuration knob for this (i.e., one that has a chance of being
> merged)?
take a look at the handling of RA messages
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/net/ipv6/ndisc.c#n1233
shows a few existing sysctl knobs for managing what is allowed and
how.
prev parent reply other threads:[~2022-08-28 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 16:29 ULA and privacy addressing Kyle Rose
2022-08-28 23:53 ` David Ahern [this message]
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=20220828235340.GA13078@u2004-local \
--to=dsahern@kernel.org \
--cc=krose@krose.org \
--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).