-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
iperf3: snd-timeout not works as expected #1858
Comments
It may be that this because iperf3 main thread is not tracking failures of the send/receive threads, the issue that PR #1654 tries to fix. It will help if you can check whether this is the problem. This can be done (on the Client side) by either:
|
Hello @davidBar-On You describe the problem very well. Here is an output from your fixed version of iperf3. It works as expected.
|
Thanks for testing. I have now re-based PR #1654 to catch up with the latest iperf3 mainline (master) branch. Since in the above output I see that there is no error message from a thread about its termination, I added such error message. I also submitted PR #1861 which adds similar error messages, since I am not sure if or when PR #1654 will be merged to the mainline. |
Here is an output from your modification:
Here is an output from server:
|
@davidBar-On , thank you very much for fixing this issue. |
@zokl, thank you for testing! I see that by mistake |
affected version: iperf3.16, iperf3.17, iperf3.18 till last commit
unaffected version: iperf3.15
kernel: Linux FTW1 5.10.221 #0 SMP Mon Jul 22 22:56:41 2024 x86_64 GNU/Linux
system: OpenWRT 22.03
iperf3 build info
If the snd-timeout parameter is set, I expect that when the interface is dropped after the timeout the iperf on the data sending side will be terminated. This does not happen.
If I restart the interface during the measurement, the server side is terminated, but the client side is not terminated.
Replication:
Server side:
Client side:
Right function in version 3.15
iperf3 3.15 build info
The text was updated successfully, but these errors were encountered: