nRF Connect v2.5.0: DTLS Connection ID not Implemented?

RE: nRF Connect v2.5.0: DTLS Connection ID not Implemented?

Edvin — Mon, 12 Feb 2024 09:56:13 GMT

Hello Nicola,

No, that API is not part of the openthread API. You need to search in the openthread documentation. The socket API that you link to is generic Zephyr API, and Zephyr is not limited to Nordic-only devices. So this would be targeting something that would typically have an ethernet port, WiFi, or some other form of IP communication.

If this is possible at all, you would need to check with Zephyr support directly. I see that there is a sample called Echo Client, which looks like it supports openthread backend by including the overlay-ot.conf.

If that doesn't work, I still suggest checking out:

https://openthread.io/reference/group/api-coap-secure

Best regards,

Edvin

RE: nRF Connect v2.5.0: DTLS Connection ID not Implemented?

nikpov — Mon, 12 Feb 2024 09:25:35 GMT

It should be something like

int enable_cid = 2;

ret = setsockopt(sock, SOL_TLS, TLS_DTLS_CID, &enable_cid, sizeof(enable_cid));

as specified here.

OpenThread cannot call such API as the source code to implement it is just not there., as I already stated.

BR,
Nicola

RE: nRF Connect v2.5.0: DTLS Connection ID not Implemented?

Edvin — Mon, 12 Feb 2024 09:03:27 GMT

Hello Nicola,

sorry for the late reply. What API specifically are you missing? I guess you would have to do some configurations before building the application so that the openthread stack is built with the correct settings.

Best regards,

Edvin

RE: nRF Connect v2.5.0: DTLS Connection ID not Implemented?

nikpov — Mon, 05 Feb 2024 09:07:49 GMT

Hi Edvin,

We are already using with success the whole stack, including CoAP, mbedTLS and OpenThread.

However, OpenThread API itself gives no means to enable the Connection ID feature for a DTLS session.

As specified by the link within my first message, that shall be enabled by directly acting onZephyr Socket API, however as said the feature is just not there, according to latest nRF Connect SDK source code.

BR,

Nicola

RE: nRF Connect v2.5.0: DTLS Connection ID not Implemented?

Edvin — Fri, 02 Feb 2024 14:11:21 GMT

Hello Nicola,

I see. I suggest you check out the OpenThread API documentation:

https://openthread.io/reference/group/api-coap-secure

In addition to this section from our documentation on how to modify the OpenThread stack to add support for COAP and Mbed TLS.

Best regards,

Edvin

RE: nRF Connect v2.5.0: DTLS Connection ID not Implemented?

nikpov — Thu, 01 Feb 2024 14:58:25 GMT

Hi Edvin,

you are right, I forgot mentioning we are working with CoAP/DTLS over Thread (OpenThread).

Given such context, can you help us with the resolution of mentioned problem?

Best Regards,

Nicola

RE: nRF Connect v2.5.0: DTLS Connection ID not Implemented?

Edvin — Thu, 01 Feb 2024 14:54:57 GMT

Hello Nicola,

I am not sure what you mean here. You want to do DTLS over what? WiFi? The nRF5340 doesn't have Wifi. Only BLE, Zigbee and Thread. Do you mean that you want to use OpenThread for DTLS? If so, you would need an OpenThread network, but since you didn't mention Thread/openthread, I am not sure whether this is what you actually mean.

Best regards,

Edvin