From: David Ahern <dsahern@kernel.org>
To: Alex Henrie <alexhenrie24@gmail.com>,
netdev@vger.kernel.org, dan@danm.net, bagasdotme@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jikos@kernel.org
Subject: Re: [PATCH net-next v2 2/3] net: ipv6/addrconf: introduce a regen_min_advance sysctl
Date: Wed, 14 Feb 2024 08:39:36 -0700 [thread overview]
Message-ID: <705cac76-dc97-4bfa-9340-1dbaa5de3b2b@kernel.org> (raw)
In-Reply-To: <20240214062711.608363-3-alexhenrie24@gmail.com>
On 2/13/24 11:26 PM, Alex Henrie wrote:
> In RFC 8981, REGEN_ADVANCE cannot be less than 2 seconds, and the RFC
> does not permit the creation of temporary addresses with lifetimes
> shorter than that:
>
>> When processing a Router Advertisement with a
>> Prefix Information option carrying a prefix for the purposes of
>> address autoconfiguration (i.e., the A bit is set), the host MUST
>> perform the following steps:
>
>> 5. A temporary address is created only if this calculated preferred
>> lifetime is greater than REGEN_ADVANCE time units.
>
> However, some users want to change their IPv6 address as frequently as
> possible regardless of the RFC's arbitrary minimum lifetime. For the
> benefit of those users, add a regen_min_advance sysctl parameter that
> can be set to below or above 2 seconds.
>
> Link: https://datatracker.ietf.org/doc/html/rfc8981
> Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
> ---
> Documentation/networking/ip-sysctl.rst | 10 ++++++++++
> include/linux/ipv6.h | 1 +
> include/net/addrconf.h | 5 +++--
> net/ipv6/addrconf.c | 11 ++++++++++-
> 4 files changed, 24 insertions(+), 3 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2024-02-14 15:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 6:10 [PATCH net-next 1/3] net: ipv6/addrconf: ensure that regen_advance is at least 2 seconds Alex Henrie
2024-02-09 6:10 ` [PATCH net-next 2/3] net: ipv6/addrconf: introduce a regen_min_advance sysctl Alex Henrie
2024-02-13 15:36 ` David Ahern
2024-02-09 6:10 ` [PATCH net-next 3/3] net: ipv6/addrconf: clamp preferred_lft to the minimum required Alex Henrie
2024-02-13 10:13 ` Paolo Abeni
2024-02-13 15:40 ` David Ahern
2024-02-13 21:07 ` Dan Moulding
2024-02-13 15:35 ` [PATCH net-next 1/3] net: ipv6/addrconf: ensure that regen_advance is at least 2 seconds David Ahern
2024-02-14 6:26 ` [PATCH net-next v2 0/3] net: ipv6/addrconf: ensure that temporary addresses' preferred lifetimes are long enough Alex Henrie
2024-02-14 6:26 ` [PATCH net-next v2 1/3] net: ipv6/addrconf: ensure that regen_advance is at least 2 seconds Alex Henrie
2024-02-14 15:38 ` David Ahern
2024-02-14 6:26 ` [PATCH net-next v2 2/3] net: ipv6/addrconf: introduce a regen_min_advance sysctl Alex Henrie
2024-02-14 15:39 ` David Ahern [this message]
2024-02-14 6:26 ` [PATCH net-next v2 3/3] net: ipv6/addrconf: clamp preferred_lft to the minimum required Alex Henrie
2024-02-14 15:40 ` David Ahern
2024-02-15 14:50 ` [PATCH net-next v2 0/3] net: ipv6/addrconf: ensure that temporary addresses' preferred lifetimes are long enough patchwork-bot+netdevbpf
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=705cac76-dc97-4bfa-9340-1dbaa5de3b2b@kernel.org \
--to=dsahern@kernel.org \
--cc=alexhenrie24@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=dan@danm.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jikos@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).