Hi ciruzzo,
I am currently exploring what the issue might be here. If windows does not support SO_REUSEPORT have you considered using the client-dtls-nonblocking in conjunction with the normal server-dtls?
The reason I ask is the non-blocking client will continue to attempt to write until it succeeds and the normal server-dtls runs in an infinite loop just watching for messages on the open socket. Due to the nature of DTLS potentially infinite clients could connect to the server-dtls and send a message/get a response from the server. The server would eventually get the Datagrams out of the file descriptor when it looped back around and handle each request in turn.
Kind Regards,
Kaleb
Hi Kaleb,
Thank you for your answer.
I'm going to modifiy the server-dtls example in order to hadle multiple clients.
I will let you know if it works.
Hi again ciruzzo,
Just as a follow up we are curious what your project entails. We ask because DTLS is a beast in and of it's own. Furthermore multi-threading in DTLS is a problem not easily solved. It has peaked both mine, and others interests here at wolfSSL and we'd enjoy further information regarding your project motivation.
Kind Regards,
Kaleb
Ok, my objective a is to provide an encrypted connection under Windows OS among a server and several clients, over a mobile network. At the beginning I choosed TLS protocol, but the bandwith for each client is very poor (4 kbit/s) and the rate of lost packets is significant. I'm not satisfied of the packet retransmission performed by TCP, because sometimes it takes a very long time to recover. Moreover I don't need retransmission, because it is already performed at application layer. Therefore I switched to DTLS, in order to achieve better performance avoiding useless retransmissions. Before WolfSSL, I tried OpenSSL, but I was not able to make it working with DTLS.
Regards
Ciruzzo