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: Re: [PATCH 2/3] icmp: define probe message types
Date: Fri, 13 Nov 2020 12:54:23 -0800 [thread overview]
Message-ID: <30091c4aab58aba9e75fd591becf7a91cd7b46e9.camel@gmail.com> (raw)
In-Reply-To: <20201113050241.8218-1-andreas.a.roeseler@gmail.com>
On Thu, 2020-11-12 at 21:02 -0800, Andreas Roeseler wrote:
> Types of ICMP Extended Echo Request and ICMP Extended Echo Reply are
> defined in sections 2 and 3 of RFC 8335.
>
> Signed-off-by: Andreas Roeseler <andreas.a.roeseler@gmail.com>
> ---
> include/uapi/linux/icmp.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/include/uapi/linux/icmp.h b/include/uapi/linux/icmp.h
> index fb169a50895e..6cabb6acc156 100644
> --- a/include/uapi/linux/icmp.h
> +++ b/include/uapi/linux/icmp.h
> @@ -66,6 +66,10 @@
> #define ICMP_EXC_TTL 0 /* TTL count
> exceeded */
> #define ICMP_EXC_FRAGTIME 1 /* Fragment Reass time
> exceeded */
>
> +/* Codes for EXT_ECHO (Probe). */
> +#define ICMP_EXT_ECHO 42
> +#define ICMP_EXT_ECHOREPLY 43
> +
>
> struct icmphdr {
> __u8 type;
next prev parent reply other threads:[~2020-11-13 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1605238003.git.andreas.a.roeseler@gmail.com>
[not found] ` <20201113073230.3ecd6f0d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
2020-11-13 20:53 ` [PATCH 0/3] Add support for sending RFC8335 PROBE messages Andreas Roeseler
2020-11-13 21:33 ` Jakub Kicinski
[not found] ` <20201113050234.8165-1-andreas.a.roeseler@gmail.com>
2020-11-13 20:54 ` [PATCH 1/3] net: add support for sending probe messages Andreas Roeseler
[not found] ` <20201113050241.8218-1-andreas.a.roeseler@gmail.com>
2020-11-13 20:54 ` Andreas Roeseler [this message]
[not found] ` <20201113050247.8273-1-andreas.a.roeseler@gmail.com>
2020-11-13 20:54 ` [PATCH 3/3] ICMPv6: define probe message types Andreas Roeseler
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=30091c4aab58aba9e75fd591becf7a91cd7b46e9.camel@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).