From: Andreas Roeseler <andreas.a.roeseler@gmail.com>
To: davem@davemloft.net
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 net-next 2/3] ICMPv6: define PROBE message types
Date: Tue, 17 Nov 2020 16:47:18 -0800 [thread overview]
Message-ID: <a810d633e2fdd0b907ed91d3c5d3d2c7c2dd3564.1605659597.git.andreas.a.roeseler@gmail.com> (raw)
In-Reply-To: <cover.1605659597.git.andreas.a.roeseler@gmail.com>
The types of ICMPV6 Extended Echo Request and ICMPV6 Extended Echo Reply
are defined in sections 2 and 3 of RFC8335.
Signed-off-by: Andreas Roeseler <andreas.a.roeseler@gmail.com>
---
Changes since v1:
- Switch to correct base tree
Changes since v2:
- Switch to net-next tree 67c70b5eb2bf7d0496fcb62d308dc3096bc11553
Changes since v3:
- Reorder patches to add defines first
---
include/uapi/linux/icmpv6.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/include/uapi/linux/icmpv6.h b/include/uapi/linux/icmpv6.h
index 0564fd7ccde4..54dbafdedca1 100644
--- a/include/uapi/linux/icmpv6.h
+++ b/include/uapi/linux/icmpv6.h
@@ -140,6 +140,12 @@ struct icmp6hdr {
#define ICMPV6_UNK_OPTION 2
#define ICMPV6_HDR_INCOMP 3
+/*
+ * Codes for EXT_ECHO (Probe)
+ */
+#define ICMPV6_EXT_ECHO_REQUEST 160
+#define ICMPV6_EXT_ECHO_REPLY 161
+
/*
* constants for (set|get)sockopt
*/
--
2.29.2
next prev parent reply other threads:[~2020-11-18 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 0:46 [PATCH v4 net-next 0/3] add support for sending RFC8335 PROBE Andreas Roeseler
2020-11-18 0:47 ` [PATCH v4 net-next 1/3] icmp: define PROBE message types Andreas Roeseler
2020-11-18 0:47 ` Andreas Roeseler [this message]
2020-11-18 0:47 ` [PATCH v4 net-next 3/3] net: add support for sending RFC8335 PROBE Andreas Roeseler
2020-11-20 3:51 ` [PATCH v4 net-next 0/3] " David Ahern
2020-11-20 4:01 ` David Ahern
2020-11-20 17:27 ` Andreas Roeseler
2020-11-20 20:22 ` 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=a810d633e2fdd0b907ed91d3c5d3d2c7c2dd3564.1605659597.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=linux-kernel@vger.kernel.org \
--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).