-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DTLS Connection id (CID) #1472
Comments
Yes, there is support for CID in Mbed TLS. The Mbed TLS library needs to be built with |
Thank you for answer, Do i need to do anything additional in my project, which i am utilizing libcoap? |
Other than the 2 things that need to be done (Build and install the Mbed TLS library with Connection ID enabled, and build libcoap for Mbed TLS using the updated Mbed TLS library), I am not aware of anything else. See #1153 . |
I am bit lost, client and server negotiated usage of CID successfully, but when client is reconnecting and starts sending messages, i get these when debugging is on: Full log is in attachment. |
I'm trying to reproduce your situation. To get rid of the Handshake dropped messages so that they are processed, can you please try the following code change
|
To prevent session closing after connecting to server, i am using following function when initializing server: New log is in attachment. |
@juhis-o Please try out #1482 where the server now updates the the existing CoAP session IP tuple with the new set of IP addresses the client is using, thus keeping the DTLS session information previously used across changing IP tuples. The examples coap-client has a new option. |
It works now! Thank you for addressing issue this quickly! |
Hey
Is there support for CoAP DTLS Connection ID?
I found some mentions about this in coap_dtls_internal.h and coap__mbedtls_8c_source.html files, but it is not quite clear if this feature is available.
If it is, how do i set it up?
The text was updated successfully, but these errors were encountered: