DAST: Iperf - -c command - jstuder --at-- harris.com
>Date: Thu, 2 Feb 2006 08:31:18 -0600
>To: jstuder --at-- harris.com
>Subject: DAST: Iperf - -c command - jstuder --at-- harris.com
>
>
>Contacting DAST re: Request for information about Iperf
>From: John Studer <jstuder --at-- harris.com>
>
>Subject: -c command
>
>Question/Comment:
>This question relates to the -c command placing Iperf in the client mode.
Your site's note on the command is:
>
>If Iperf is in server mode, then specifying a host with -c will limit the
connections that Iperf will accept to the host specified. Does not work
well for UDP.
>
>The first part of the note about specifying a -c for a machine in the
server mode is self explanatory and it makes sense that things would not
work well doing this. However, for the note "Does not work well for UDP"
does this apply for all type of UDP transactions not just erroniously
setting -c while in the server mode? In the lab we notice tremendous
performance differences between UDP and TCP with the exact same
experimental setup. Maybe this could be that Iperf does not work well in
the UDP mode.
>
>
--
Mitch Kutzko | mitch --at-- dast.nlanr.net | mitch --at-- ncsa.uiuc.edu | 217-333-1199
http://hobbes.ncsa.uiuc.edu/