From: David Ahern <dsahern@gmail.com>
To: Andreas Roeseler <andreas.a.roeseler@gmail.com>, 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: Re: [PATCH v4 net-next 0/3] add support for sending RFC8335 PROBE
Date: Thu, 19 Nov 2020 21:01:25 -0700 [thread overview]
Message-ID: <8ac13fd8-69ac-723d-d84d-c16c4fa0a9ab@gmail.com> (raw)
In-Reply-To: <b4ce1651-4e45-52eb-7b2e-10075890e382@gmail.com>
On 11/19/20 8:51 PM, David Ahern wrote:
> On 11/17/20 5:46 PM, Andreas Roeseler wrote:
>> The popular utility ping has several severe limitations such as the
>> inability to query specific interfaces on a node and requiring
>> bidirectional connectivity between the probing and the probed
>> interfaces. RFC8335 attempts to solve these limitations by creating the
>> new utility PROBE which is a specialized ICMP message that makes use of
>> the ICMP Extension Structure outlined in RFC4884.
>>
>> This patchset adds definitions for the ICMP Extended Echo Request and
>> Reply (PROBE) types for both IPv4 and IPv6. It also expands the list of
>> supported ICMP messages to accommodate PROBEs.
>>
>
> You are updating the send, but what about the response side?
>
you also are not setting 'ICMP Extension Structure'. From:
https://tools.ietf.org/html/rfc8335
o ICMP Extension Structure: The ICMP Extension Structure identifies
the probed interface.
Section 7 of [RFC4884] defines the ICMP Extension Structure. As per
RFC 4884, the Extension Structure contains exactly one Extension
Header followed by one or more objects. When applied to the ICMP
Extended Echo Request message, the ICMP Extension Structure MUST
contain exactly one instance of the Interface Identification Object
(see Section 2.1).
next prev parent reply other threads:[~2020-11-20 4:01 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 ` [PATCH v4 net-next 2/3] ICMPv6: " Andreas Roeseler
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 [this message]
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=8ac13fd8-69ac-723d-d84d-c16c4fa0a9ab@gmail.com \
--to=dsahern@gmail.com \
--cc=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).