From: Arun Ajith S <aajith@arista.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
dsahern@kernel.org, yoshfuji@linux-ipv6.org, kuba@kernel.org,
pabeni@redhat.com, corbet@lwn.net, prestwoj@gmail.com,
gilligan@arista.com, noureddine@arista.com, gk@arista.com
Subject: Re: [PATCH net-next v4] net/ipv6: Introduce accept_unsolicited_na knob to implement router-side changes for RFC9131
Date: Thu, 14 Apr 2022 14:29:01 +0530 [thread overview]
Message-ID: <CAOvjArTBoxSnX_ck_pW9Fq1cVXtT1sQ9zVHL207fdwj5v5iygQ@mail.gmail.com> (raw)
In-Reply-To: <0bf37720-870a-9dde-d825-92e12633ce38@gmail.com>
Thank you.
Do I have to post a v5 with the fixup ?
-Arun
-Arun
On Thu, Apr 14, 2022 at 11:42 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> On 4/14/22 09:56, Arun Ajith S wrote:
> > Add a new neighbour cache entry in STALE state for routers on receiving
> > an unsolicited (gratuitous) neighbour advertisement with
> > target link-layer-address option specified.
> > This is similar to the arp_accept configuration for IPv4.
> > A new sysctl endpoint is created to turn on this behaviour:
> > /proc/sys/net/ipv6/conf/interface/accept_unsolicited_na.
> >
>
> Hi,
>
> Building the documentation (htmldocs) with this patch, I got:
>
> /home/bagas/repo/linux-stable/Documentation/networking/ip-sysctl.rst:2475:
> WARNING: Unexpected indentation.
> /home/bagas/repo/linux-stable/Documentation/networking/ip-sysctl.rst:2477:
> WARNING: Unexpected indentation.
> /home/bagas/repo/linux-stable/Documentation/networking/ip-sysctl.rst:2481:
> WARNING: Unexpected indentation.
> /home/bagas/repo/linux-stable/Documentation/networking/ip-sysctl.rst:2482:
> WARNING: Block quote ends without a blank line; unexpected unindent.
>
> I have applied following fixup.
>
> ---- 8> ----
> From 304846b43a9f962f53f3841afabfd597b3b80951 Mon Sep 17 00:00:00 2001
> From: Bagas Sanjaya <bagasdotme@gmail.com>
> Date: Thu, 14 Apr 2022 12:59:46 +0700
> Subject: [PATCH] fixup for "net/ipv6: Introduce accept_unsolicited_na knob to
> implement router-side changes for RFC9131"
>
> Fix the simple table syntax.
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/networking/ip-sysctl.rst | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/networking/ip-sysctl.rst b/Documentation/networking/ip-sysctl.rst
> index 9e17efe343a..433f2e4a5fe 100644
> --- a/Documentation/networking/ip-sysctl.rst
> +++ b/Documentation/networking/ip-sysctl.rst
> @@ -2472,13 +2472,17 @@ accept_unsolicited_na - BOOLEAN
> unsolicited neighbour advertisement with target link-layer address option
> specified. This is as per router-side behavior documented in RFC9131.
> This has lower precedence than drop_unsolicited_na.
> +
> + ==== ====== ====== ==============================================
> drop accept fwding behaviour
> ---- ------ ------ ----------------------------------------------
> 1 X X Drop NA packet and don't pass up the stack
> 0 0 X Pass NA packet up the stack, don't update NC
> 0 1 0 Pass NA packet up the stack, don't update NC
> 0 1 1 Pass NA packet up the stack, and add a STALE
> - NC entry
> + NC entry
> + ==== ====== ====== ==============================================
> +
> This will optimize the return path for the initial off-link communication
> that is initiated by a directly connected host, by ensuring that
> the first-hop router which turns on this setting doesn't have to
>
> base-commit: 38e01f46e0e7f88b92ca0b3f52ac6b9909ed413b
> --
> An old man doll... just what I always wanted! - Clara
>
> Thanks.
>
> --
> An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-04-14 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 2:56 [PATCH net-next v4] net/ipv6: Introduce accept_unsolicited_na knob to implement router-side changes for RFC9131 Arun Ajith S
2022-04-14 6:11 ` Bagas Sanjaya
2022-04-14 8:59 ` Arun Ajith S [this message]
2022-04-14 9:33 ` Jakub Kicinski
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=CAOvjArTBoxSnX_ck_pW9Fq1cVXtT1sQ9zVHL207fdwj5v5iygQ@mail.gmail.com \
--to=aajith@arista.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gilligan@arista.com \
--cc=gk@arista.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noureddine@arista.com \
--cc=pabeni@redhat.com \
--cc=prestwoj@gmail.com \
--cc=yoshfuji@linux-ipv6.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).