Re: specifying finite runtime

To: iperf-users --at-- dast.nlanr.net, <iperf-users --at-- dast.nlanr.net>
Subject: Re: specifying finite runtime
From: Jeff Schultz <jschultz --at-- qualcomm.com>
Date: Wed, 28 Apr 2004 16:43:51 -0700
Content-type: multipart/alternative;boundary="=====================_264949265==.ALT"
In-reply-to: <0320111483D8B84AAAB437215BBDA526848233 --at-- NAEX01.na.qualcomm.com>
References: <0320111483D8B84AAAB437215BBDA526848233 --at-- NAEX01.na.qualcomm.com>
Reply-to: iperf-users --at-- dast.nlanr.net
Sender: owner-iperf-users --at-- dast.nlanr.net

I'm pretty sure you have to specify the -t option for the server as well if doing bi-directional. The default transfer time is 10 seconds so it sounds like you're hitting that.

Jeff

At 03:59 PM 4/28/2004, Craig, Dave wrote:

I’m running dual mode tests and I noticed that the server does not run for the same length of time as the client. For instance,

server% iperf –uVsB 3ffe:502:ffff::2

client% iperf –c3ffe:502:ffff::2 –V –t5 –du –l128

The client transmits for 5 seconds, and the server transmits for 10 seconds. Am I overlooking something in the command-line arguments?

Thank you,
Dave Craig

QUALCOMM Incorporated

References:
- specifying finite runtime
  - From: "Craig, Dave"

Prev by Date: specifying finite runtime
Next by Date: RE: specifying finite runtime
Previous by thread: specifying finite runtime
Next by thread: RE: specifying finite runtime

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