From: Florian Weimer <fweimer@redhat.com>
To: Andreas Roeseler via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Add RFC 8335 Definitions from Linux 5.12
Date: Tue, 20 Apr 2021 18:39:02 +0200 [thread overview]
Message-ID: <87im4gvrkp.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20210413224255.1746849-1-andreas.a.roeseler@gmail.com> (Andreas Roeseler via Libc-alpha's message of "Tue, 13 Apr 2021 17:42:55 -0500")
* Andreas Roeseler via Libc-alpha:
> diff --git a/sysdeps/gnu/netinet/ip_icmp.h b/sysdeps/gnu/netinet/ip_icmp.h
> index 5db7ac7c37..1fd6317df4 100644
> --- a/sysdeps/gnu/netinet/ip_icmp.h
> +++ b/sysdeps/gnu/netinet/ip_icmp.h
> @@ -89,6 +89,23 @@ struct icmphdr
> #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
> +#define ICMP_EXT_MAL_QUERY 1 /* Malformed Query */
> +#define ICMP_EXT_NO_IF 2 /* No such Interface */
> +#define ICMP_EXT_NO_TABLE_ENT 3 /* No such Table Entry */
> +#define ICMP_EXT_MULT_IFS 4 /* Multiple Interfaces Satisfy Query */
> +
> +/* Constants for EXT_ECHO (PROBE) */
> +#define EXT_ECHOREPLY_ACTIVE (1 << 2)/* active bit in reply message */
> +#define EXT_ECHOREPLY_IPV4 (1 << 1)/* ipv4 bit in reply message */
> +#define EXT_ECHOREPLY_IPV6 1 /* ipv6 bit in reply message */
> +#define EXT_ECHO_CTYPE_NAME 1
> +#define EXT_ECHO_CTYPE_INDEX 2
> +#define EXT_ECHO_CTYPE_ADDR 3
> +#define ICMP_AFI_IP 1 /* Address Family Identifier for ipv4 */
> +#define ICMP_AFI_IP6 2 /* Address Family Identifier for ipv6 */
I'm a bit surprised how the EXT_* macros step outside of the general
ICMP namespace here.
And the ICMP_EXT_* macros seem to be for different PDU fields even
though they share a common prefix (ICMP_EXT_).
Thanks,
Florian
prev parent reply other threads:[~2021-04-20 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 22:42 Andreas Roeseler
2021-04-20 15:21 ` Andreas Roeseler
2021-04-20 16:39 ` Florian Weimer [this message]
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=87im4gvrkp.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).