RE: Iperf 2.0 Beta

[Cottrell, L. <cottrell@SLAC.Stanford.EDU>]

Kevin, was/is there a new feature in 2.0 that would allow an admin to specify only one iperf server to run at a time (to help prevent a denial of service attack). I seem to recall such a feature being mentioned, but cannot find the reference. Also is there any logging of who connects, when and for what?  The idea is to have a complimentary iperf server running all the time, but to only allow one connection at a time (not sure how the client would know to try again later).

-----Original Message-----
From: Kevin Gibbs [mailto:kg...@nc...] 
Sent: Monday, December 22, 2003 1:04 PM
To: ipe...@da...; ipe...@da...
Subject: Iperf 2.0 Beta


Well there was a little bit of feedback on the previous alpha, so as my 
Christmas present to you all I have cleaned those issues up and now have 
released a beta. You can get it at:

http://dast.nlanr.net/Projects/Iperf/iperf-2.0.b.tar.gz

Kevin


Changes since 2.0.a:
Fixed single threaded compiles (use: ./configure --disable-threads ) When using -1 and (-P N) on the server the 'N' now refers to the number of 
"clients" in the sense of runs of iperf with the -c. This allows for 
multiple streams from a single client (-P) without decrementing the 'N' 
for each one.
Fixed a Summing bug

Changes from 1.7.0:
Complete rewrite!! Changed a lot!
(-1) only allows handling of a single IP at a time on the server but 
allows any number of streams from that client.
(-y x) changes reporting style to 'x' currently the only available 
additional style is 'csv' which generates CSV single line output. (-x T) eXcludes types of reports. This will remove some of the possible 
reports. 'T' can be s,c,d,v where s = Settings report, c = Connection 
report, d = Data Report, and v = Server Reports on clients for UDP. So to 
exclude settings and connection reports use (-x sc).