Open nato4r opened 4 years ago
Could you please add the following information:
I couldn't reproduce your Problem with Boost(1.72.0) and ASIO(1.16.1).
This is non-boost version of ASIO 1.16.1 and I am using Windows 10 1909.
I reproduced the Problem with windows 10, openssl 1.1.1g asio-1.16.1 but haven't found the cause yet.
I don't know how to solve it yet, but the Problem seems to be the following:
At least that's what how I currently understand it.
The examples on the windows_workarounds branch should work on Windows. The usability is not great, so I willl propably change the acceptor before merging into master.
This bug is still reproducible with Boost 1.82.0 and Windows 11. I think @sdamm's understanding is mostly correct and matches my observations as well.
One issue with the workaround is that the acceptor breaks after that. It is able to accept one DTLS connection, but then it never seems to accept any others even though async_accept has been called.
I've also found that the workaround sometimes doesn't work, but it does seem to work reliably for me when run under a debugger, so that suggests there might be a race condition here too (where the wrong socket receives a datagram). This could be part of the problem.
Hello I'm using asio example without changing anything and get this.
Error in Accept: unexpected message
Here is a screenshot.