Iperf2 has timeout problems

[mfeit-internet2]

Iperf2 seems to be having problems with the remote end dying with "process took to long to run."

[mfeit-internet2]

We'd iceboxed this because nobody had complained about it and just this morning, someone did.

Probably need to adjust the destination-side estimate of run time.

[mfeit-internet2]

This may have the same problem iperf3 did with calculating bad times.

See 417df72#diff-90b79b4771dbe6b8496e750992a37ee9

That was a slightly different problem, but the approach in fixing this should be the same.

[stanier]

Any update on this? I have a deployment that heavily relies on iperf for throughput testing and this is really slowing us down.

[mfeit-internet2]

Sorry, this one slipped through the cracks. We'd tagged it for 4.3 well before it had been decided there would be a 4.2.4 release.

4.2.4 is at the tail end of the release pipeline (and was just announced), so it's unlikely I can get the fix into that. However, I can make the adjustments and follow it up with a 4.2.5 in a few days.

[mfeit-internet2]

I have a fix for that that we'll try and get out in the next few days.

TODO:

• Need to merge this fix with 4.3.0

[mfeit-internet2]

This will be out in the next bugfix release.

[stanier]

Awesome, thank you!