-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
.net core 8 UDP Socket gets stuck on the first endpoint it sends to #99863
Comments
Tagging subscribers to this area: @dotnet/ncl |
Duplicate of #97965? |
It would be great if you can try the 9.0 build @moustakakisCon https://github.com/dotnet/installer |
this was fixes in 9.0 by #98134. Backport is waiting for approval. |
@wfurt i can confirm that in dotnet-sdk-9.0.100-preview.3.24165.20-win-x64 the issue is fixed |
Duplicate of #97965 |
Description
in .net core 8 (dotnet-sdk-8.0.203) the UDP socket will only send to the first endpoint used. trying to send to another endpoint ends up sending it in the first one used.
Reproduction Steps
[not available at the moment]
Expected behavior
Expected behaviour is for the socket to be able to send to the endpoint provided
Actual behavior
Actual behaviour is that the socket will only send to the first endpoint used.
Regression?
issue is not present in .net core 6 nor .net core 7
Known Workarounds
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: