DAST: Iperf - Possible improvement to iperf doc? - allcock --at-- mcs.anl.gov
>Date: Mon, 18 Jul 2005 19:47:25 -0500
>To: allcock --at-- mcs.anl.gov
>Subject: DAST: Iperf - Possible improvement to iperf doc? - allcock --at--
mcs.anl.gov
>
>
>Contacting DAST re: Other about Iperf
>From: Bill Allcock <allcock --at-- mcs.anl.gov>
>
>Subject: Possible improvement to iperf doc?
>
>Question/Comment:
>A question that I get asked periodically, and everytime I have to go test
it to verify, is who is transmitting and who is receiving (client vs
server). Particularly now that you have the options of reversing the
connections, does that also reverse the direction of transmission?
>
>I looked through the doc and did not see anything regarding who is
transmitting, though you clearly lay out who is connecting.
>
>So, something in the doc saying "the connecting side always sends" or "the
client side always sends" or whatever would be helpful.
>
>btw, I use iperf all the time, it is a great tool.
>
>On another note, is there any authorization when it runs as a daemon? or
can anyone who knows its there run against it? Have you ever had anyone
voice concern over potential DOS attacks via iperf? I work for Globus and
I was just wondering if you have every considered adding GSI as an option.
>
>and finally, I clicked the dast --at-- nlanr.net link on the doc page, but the
mail bounced.
>
>
--
Mitch Kutzko | mitch --at-- dast.nlanr.net | mitch --at-- ncsa.uiuc.edu | 217-333-1199
http://hobbes.ncsa.uiuc.edu/