Michael,

On 2021-07-21, Michael Richardson <mcr+i...@sandelman.ca> wrote:

> Esko Dijk <esko.d...@iotconsultancy.nl> wrote:
>     > There is already a "CoAP ping" described in RFC 7252 that can be
>     > used. It does not access any resource, just the CoAP server endpoint at
>     > CoAP message layer. As a side effect of this ping your DTLS stack will
>     > set up the connection which is handy.
>
> I recalled that later in the day that CoAP "ping" is not connected to CoAP
> "echo" :-)
> I think that there is also potentially a need for a way to debug possible MTU
> issues.
> Is there a way to use Olaf's "coap-client" to do the ping?

-K does that, see man coap-client 
(https://libcoap.net/doc/reference/develop/man_coap-client.html):

      -K interval
           Send a ping after interval seconds of inactivity. If
           not specified (or 0), keep-alive is disabled (default).

It would be not difficult to create a dedicated coap-ping, though.

> I don't see an option, and it also doesn't seem to be commonly built
> with DTLS.

It is automatically built with DTLS if you have either GnuTLS, OpenSSL,
Mbed TLS with headers installed (--enable-dtls is default).

Grüße
Olaf

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima

Reply via email to