-
-
Notifications
You must be signed in to change notification settings - Fork 114
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 - multiple handshake at the same time #109
Comments
Hm. As I know I didn't add such limitation. Do you know where this restriction comes from (line)? |
No, I didn't check the code (though I'm not too common with "go"). |
Is there a way to enable some more logging for the DTLS? |
Hi for dtls you can set logget with trace level. Like:
|
@jkralik I've noticed the same behaviour at the latest version (v2.0.3). See the log below, with DTLS trace logs, where I've ran 5 test clients in paralell against one server. This is without using the What I noticed is that the next handshake is only started after the previous one is completed. Search for the following two logs to see that behaviour.
I did notice that one requests seem to be handled while a next handshake is in progress. For this, see e.g. the 5 parallel clients with one server, DTLS trace logs enabled
|
I've created my own Attached is this workaround, which uses 1000 goroutines. @boaks maybe this will help you as well for the time being. |
I'm not common enough to |
@boaks Yeah, just copy the file somewhere in your sources. Then, instead of calling |
Thanks! |
We also face this issue. From taking a look at the code, I would spawn the go routine after the accept and not hard limit the number of routines to 1.000. Anyway we probably can share the code if we find more scalable solution :) |
Testing the coaps feature
it seems, that the server is only able to handle one DTLS handshake after the other.
Is that the intended behavior?
The text was updated successfully, but these errors were encountered: