From: Andreas Roeseler <andreas.a.roeseler@gmail.com>
To: davem@davemloft.net, kuznet@ms2.inr.ac.ru,
yoshfuji@linux-ipv6.org, kuba@kernel.org
Cc: netdev@vger.kernel.org
Subject: [PATCH net-next 3/6] net: add sysctl for enabling RFC 8335 PROBE messages
Date: Thu, 3 Dec 2020 19:16:49 -0800 [thread overview]
Message-ID: <1de8170c1b7dec795f8ca257fbd56c61c36ad5a2.1607050389.git.andreas.a.roeseler@gmail.com> (raw)
In-Reply-To: <cover.1607050388.git.andreas.a.roeseler@gmail.com>
Section 8 of RFC 8335 specifies potential security concerns of
responding to PROBE requests, and states that nodes that support PROBE
functionality MUST be able to enable/disable responses and it is
disabled by default.
Add sysctl to enable responses to PROBE messages.
Signed-off-by: Andreas Roeseler <andreas.a.roeseler@gmail.com>
---
include/net/netns/ipv4.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/net/netns/ipv4.h b/include/net/netns/ipv4.h
index 8e4fcac4df72..1d9b74228f3e 100644
--- a/include/net/netns/ipv4.h
+++ b/include/net/netns/ipv4.h
@@ -85,6 +85,7 @@ struct netns_ipv4 {
#endif
int sysctl_icmp_echo_ignore_all;
+ int sysctl_icmp_echo_enable_probe;
int sysctl_icmp_echo_ignore_broadcasts;
int sysctl_icmp_ignore_bogus_error_responses;
int sysctl_icmp_ratelimit;
--
2.25.1
next prev parent reply other threads:[~2020-12-04 3:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 3:16 [PATCH net-next 0/6] add support for RFC 8335 PROBE Andreas Roeseler
2020-12-04 3:16 ` [PATCH net-next 1/6] icmp: support for RFC 8335 Andreas Roeseler
2020-12-04 3:16 ` [PATCH net-next 2/6] ICMPv6: " Andreas Roeseler
2020-12-04 3:16 ` Andreas Roeseler [this message]
2020-12-05 5:49 ` [PATCH net-next 3/6] net: add sysctl for enabling RFC 8335 PROBE messages David Ahern
2020-12-04 3:16 ` [PATCH net-next 4/6] " Andreas Roeseler
2020-12-04 3:17 ` [PATCH net-next 5/6] net: add support for sending " Andreas Roeseler
2020-12-04 3:17 ` [PATCH net-next 6/6] icmp: add response to " Andreas Roeseler
2020-12-05 5:44 ` David Ahern
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=1de8170c1b7dec795f8ca257fbd56c61c36ad5a2.1607050389.git.andreas.a.roeseler@gmail.com \
--to=andreas.a.roeseler@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--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).