David Bar-On
David Bar-On
> How do I get that error type? #1882 shoeed two issues. One is "unable to receive cookie" that is what you got here, and the other is "unable to...
> So, some server tries to talk HTTP. Yes, "GET / HTTP/1.1 Host: 141.14.27.109:5" was sent (I assume the full port is 5201). However it does not add information about...
The tcpdump output is interesting as it shows IPv4 source adress 91.238.181.96. I will check if there is a bug in the IP addr print I added .... In any...
@paulmenzel, I have improved the verbose/debug messages, including the display of the source IP address. If you still receive these connection reports, **can you try running using this version to...
> Awesome. Thank you for your work. It seems to work now: Great. Thanks for testing. Unfortunately, I still had one issue with printing the cookie which I fixed now...
I am not from the iperf3 maintenance team, but see [this recent response](https://github.com/esnet/iperf/discussions/1851%EF%BC%89#discussioncomment-12466641) in issue #1851. Note that there are already other PRs that suggest adding UDP GSO/GRO support.
Submitted PR #1897 with a suggest enhancement to add setting the server's TCP congestion control algorithm, even when setting the algorithm by the client is not supported.
The reason for this issue is that in the multi-thread versions (starting from 3.16), iperf3 checks whether the `-n` bytes or `-k` blocks were sent only at the end of...
Submitted PR #1775 which terminates the test immediately when all data was send/received, similar to the per-3.16 versions (per-multi-thread). If possible, it would be helpful if you can test using...
No data is sent, because the 50MB (the `-n` option) are transmitted during the first interval. The problem is the test should have ended at this point and not continue...