1 Topic by Sunnysunday

(2 replies, posted in wolfSSL)

I'm using WolfSSL's Connection ID in a DTLS setup and need to maintain session continuity when the client's IP changes mid-session. I understand that Connection ID should ideally allow packets to be identified with an existing session even if the IP changes.
However, when this happens, I get "Ignored packet from invalid peer" errors. Do I need to implement additional logic to associate new packets with the existing session manually, or should WolfSSL handle this by default with Connection ID?

Go to forum: wolfSSL

2 Reply by Sunnysunday

(4 replies, posted in wolfSSL)

Does the WolfSSL port for Zephyr support the DTLS Connection ID feature?
I’m aware that the mainline WolfSSL library supports Connection ID in its latest releases, but I want to confirm if this functionality is available and stable in the Zephyr environment.

Go to forum: wolfSSL

3 Reply by Sunnysunday

(4 replies, posted in wolfSSL)

Hi,

Thanks for answer. That's good news!

I am a student of computer science writing a Bachelor Thesis on the performance of DTLS (both v1.2 and v1.3) with and without ConnectionID over Narrowband-IoT networks. I will be using the Nordic Thingy:91 and wolfSSL to test that with CoAP data.

Go to forum: wolfSSL

4 Topic by Sunnysunday

(4 replies, posted in wolfSSL)

Is ConnectionID in WolfSSL only supported for DTLSv1.3 and not for DTLS1.2?

Go to forum: wolfSSL