DAST: Iperf - ian_willumsen@transcanada.com

[Mitch K. <mi...@nc...>]

>Date: Mon, 22 Nov 2004 14:11:26 -0600
>From: Apache <ap...@nc...>
>To: ian...@tr...
>Subject: DAST: Iperf - ian...@tr...
>
>
>Contacting DAST re: Feature request about Iperf
>From: Ian Willumsen <ian...@tr...>
>
>Question/Comment:
>Hi!
>
>First of all: many, many thanks for creating this tool.  It works great!
I tell everyone within telecom circles who care about testing performance
to use your tool!
>
>I do have a feature request…
>
>The IPERF’s –r functionality is useful, where you can setup another TCP
session from the server to the client.
>
>In Firewalled environments, it’s (usually) possible to initiate an IPERF
TCP session from within the trusted inside network to an outside server to
obtain TCP performance results.  It’s entirely another matter if you use
the –r option.  Most firewalled environments don’t allow the outside
machine to initiate a TCP session to port 5001 on the inside network.
>
>It should be possible to have the flow reverse within the same established
TCP session from client (inside) to server (outside), so that the same
State table entry in the firewall gets used, and then I/we would get the
same information about the uplink performance without starting a new TCP
session.
>
>Most of the time I don’t need this functionality (say over VPNs or in the
clear), but there are times this would be really really handy.
>
>Thoughts?
>
>Regards,
>Ian.
>
>
>
--
Mitch Kutzko | mi...@da... | mi...@nc... | 217-333-1199
Project: http://dast.nlanr.net/  |  Personal: http://hobbes.ncsa.uiuc.edu/