iperf server bug w/ repeated connections?

To: iperf-users --at-- dast.nlanr.net
Subject: iperf server bug w/ repeated connections?
From: Avram Dorfman <dorfman --at-- est.org>
Date: Fri, 15 Jun 2007 07:56:28 -0400
Content-transfer-encoding: 7bit
Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Reply-to: iperf-users --at-- dast.nlanr.net
Sender: owner-iperf-users --at-- dast.nlanr.net

Hello,

I seem to be experiencing a server bug when using reporting intervals.

On the first connection from a client, everything is fine.

If the client dies, maybe only if it dies ungracefully, the next time a client connects, the server seems to begin with the time interval that the previous client ended with. So if the first client ran for 200 seconds, and I have a 1 second reporting interval, I see 200 reports whiz by with all-zero data in them before I start seeing real reports.

Unfortunately, when the new client terminates, the erroneous time is included in the final report calculations by the server.

Anyone else experience this? Anyone figure out a simple fix I can stick in the code for it?

Thanks,
Avram

Follow-Ups:
- Re: iperf server bug w/ repeated connections?
  - From: Avram Dorfman

Prev by Date: Re: simulating network data
Next by Date: Re: iperf server bug w/ repeated connections?
Previous by thread: Measure the latency for a specific throughput/datarate method
Next by thread: Re: iperf server bug w/ repeated connections?

Other Mailing lists | Author Index | Date Index | Subject Index | Thread Index