Open mregen opened 2 months ago
Recently I noticed again these bursts of retransmissions in a Wireshark log. This behavior may have to do with large chunks that the .NET stack defaults to (65535). Test with different defaults (8k) should show if this is reproducible.
Type of issue
Current Behavior
Observing wireshark logs when a .NET client or server is involved, sometimes contains a lot of TCP retransmissions.
It doesn't cause functional issues but seems incorrect and the root cause is yet unknown.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Anything else?
No response