netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Subject: [PATCH v2 net-next 3/3] ICMPv6: define probe message types
Date: Fri, 13 Nov 2020 19:24:17 -0800	[thread overview]
Message-ID: <03d35bcb7aa843ede4fb3bc224b7eba85c12d522.1605323689.git.andreas.a.roeseler@gmail.com> (raw)
In-Reply-To: <cover.1605323689.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
---
 include/linux/icmpv6.h | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/include/linux/icmpv6.h b/include/linux/icmpv6.h
index ba45e6bc076..c6186774584 100644
--- a/include/linux/icmpv6.h
+++ b/include/linux/icmpv6.h
@@ -137,6 +137,12 @@ static inline struct icmp6hdr *icmp6_hdr(const struct sk_buff *skb)
 #define ICMPV6_UNK_NEXTHDR		1
 #define ICMPV6_UNK_OPTION		2
 
+/*
+ *	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


  parent reply	other threads:[~2020-11-14  3:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14  3:23 [PATCH v2 net-next 0/3] Add support for sending RFC8335 PROBE Andreas Roeseler
2020-11-14  3:24 ` [PATCH v2 net-next 1/3] net: add support for sending probe messages Andreas Roeseler
2020-11-14  3:24 ` [PATCH v2 net-next 2/3] icmp: define probe message types Andreas Roeseler
2020-11-14  3:24 ` Andreas Roeseler [this message]
2020-11-14 17:46   ` [PATCH v2 net-next 3/3] ICMPv6: " 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=03d35bcb7aa843ede4fb3bc224b7eba85c12d522.1605323689.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).