You are not logged in. Please login or register.
Active topics Unanswered topics
Welcome to the wolfSSL Forums!
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
References
Stable Releases - download stable product releases.
Development Branch - latest development branch on GitHub.
wolfSSL Manual - wolfSSL (formerly CyaSSL) product manual and API reference.
Search options
Hi,
I am working on building a DTLS client with C#.
It happens that if the server is not running, my client will block at connect() --...--> amtRecv = con.Receive(msg, msg.Length, 0);, which is reasonable in blocking IO. However, when I tried to turn to non-blocking IO, I cannot find wolfSSL_set_using_nonblock in the C# wrapper. I looked up and found the example of IOcallback: https://github.com/wolfSSL/wolfssl/blob … llbacks.cs.
However, I am not really understand how should I use it for setting non-blocking socket. Is this right solution? And is there any example?
After all, it will be great if there is same approach for wrapper to set non-blocking IO.
Thanks!
Hello,
I am trying to build a pair of server and client using DTLS with CSharp wrapper.
However, when enabling DTLS for client, I cannot find the method
.
(I refer to the code in wolfssl-example/dtls/client-dtls.c since there are no client code in wrapper.)
What method should I use to set the target address for a DTLS client?
Thank you!
Sunny
Posts found: 2
Generated in 0.015 seconds (96% PHP - 4% DB) with 4 queries