Mailing List for the Bandwidth Testing Tool Iperf

Gilles Ganault | 4 Jul 2011 15:53

[2.0.5] "-r" causes iperf to crash

Hello,

I'm running iperf on a Ubuntu server and on an appliance running uClinux.

While using UDP works fine, and TCP also works fine when using the 
"-d" option, I notice that using the "-r" option causes the server to 
crash if ran after "-d":

========================================
server> iperf -s

OK client> iperf -c 192.168.0.3 -t 30 -i 1 -r

OK client> iperf -c 192.168.0.3 -t 30 -i 1 -d

NOK client> iperf -c 192.168.0.3 -t 30 -i 1 -r

**************** CLIENT
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
connect failed: Connection refused
------------------------------------------------------------
Client connecting to 192.168.0.3, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
write1 failed: Broken pipe
[  5] local 0.0.0.0 port 58085 connected with 192.168.0.3 port 5001
write2 failed: Broken pipe

(Continue reading)

headers

Harkeerat Bedi | 6 Jul 2011 00:49

iPerf 2.0.5, add additional information in server output.

Dear iPerf users,

Is there a way to edit the amount of information displayed when iPerf is run in server mode?

Following is the default information displayed, when iPerf is run in server mode:

$ iperf -s -u -i 1 -f mb

------------------------------------------------------------

Server listening on UDP port 5001

Receiving 1470 byte datagrams

UDP buffer size: 0.11 MByte (default)

------------------------------------------------------------

[ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams

[ 3] 0.0- 1.0 sec 0.12 MBytes 1.05 Mbits/sec 0.334 ms 0/ 89 (0%)

[ 3] 1.0- 2.0 sec 0.12 MBytes 1.05 Mbits/sec 0.329 ms 0/ 89 (0%)

[ 3] 2.0- 3.0 sec 0.12 MBytes 1.05 Mbits/sec 0.334 ms 0/ 89 (0%)

[ 3] 3.0- 4.0 sec 0.12 MBytes 1.05 Mbits/sec 0.331 ms 0/ 89 (0%)

[ 3] 4.0- 5.0 sec 0.12 MBytes 1.05 Mbits/sec 0.340 ms 0/ 89 (0%)

[ 3] 5.0- 6.0 sec 0.13 MBytes 1.06 Mbits/sec 0.347 ms 0/ 90 (0%)

[ 3] 6.0- 7.0 sec 0.12 MBytes 1.05 Mbits/sec 0.341 ms 0/ 89 (0%)

[ 3] 7.0- 8.0 sec 0.12 MBytes 1.05 Mbits/sec 0.349 ms 0/ 89 (0%)

[ 3] 8.0- 9.0 sec 0.12 MBytes 1.05 Mbits/sec 0.318 ms 0/ 89 (0%)

[ 3] 9.0-10.0 sec 0.12 MBytes 1.05 Mbits/sec 0.326 ms 0/ 89 (0%)

[ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec 0.348 ms 0/ 893 (0%)

Is there a way I could change the output to something like this:

[ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams

[ 3] 0.0- 1.0 sec 0.12 MBytes 1.05 Mbits/sec 0.334 ms 0/ 89 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ 3] 1.0- 2.0 sec 0.12 MBytes 1.05 Mbits/sec 0.329 ms 0/ 89 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ 3] 2.0- 3.0 sec 0.12 MBytes 1.05 Mbits/sec 0.334 ms 0/ 89 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ 3] 3.0- 4.0 sec 0.12 MBytes 1.05 Mbits/sec 0.331 ms 0/ 89 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ 3] 4.0- 5.0 sec 0.12 MBytes 1.05 Mbits/sec 0.340 ms 0/ 89 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ 3] 5.0- 6.0 sec 0.13 MBytes 1.06 Mbits/sec 0.347 ms 0/ 90 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ 3] 6.0- 7.0 sec 0.12 MBytes 1.05 Mbits/sec 0.341 ms 0/ 89 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ 3] 7.0- 8.0 sec 0.12 MBytes 1.05 Mbits/sec 0.349 ms 0/ 89 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ 3] 8.0- 9.0 sec 0.12 MBytes 1.05 Mbits/sec 0.318 ms 0/ 89 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ 3] 9.0-10.0 sec 0.12 MBytes 1.05 Mbits/sec 0.326 ms 0/ 89 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

[ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec 0.348 ms 0/ 893 (0%) [ 3] local 10.1.2.3 port 5001 connected with 10.1.1.4 port 52551

I want to get the source and destination IP addresses and port numbers on each line, as shown above. I tried to edit the following structs in Reporter.c by including a call to the function "reporter_reportpeer", however it did not help.

report_statistics statistics_reports[kReport_MAXIMUM] = {

reporter_printstats,

reporter_reportpeer,

CSV_stats

};

report_serverstatistics serverstatistics_reports[kReport_MAXIMUM] = {

reporter_serverstats,

reporter_reportpeer,

CSV_serverstats

};

Is there a way I can get the source and destination IP addresses and port numbers on each line? Any help regarding this subject will be highly appreciated.

Thank you,

Regards,
Harkeerat Bedi

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2

_______________________________________________
Iperf-users mailing list
Iperf-users@...
https://lists.sourceforge.net/lists/listinfo/iperf-users

headers

Gary Gatten | 6 Jul 2011 01:18

Re: iPerf 2.0.5, add additional information in server output.

I’m sure there is a way, but why? It’s redundant info. If nothing else you could pass it through sed/awk/etc and tweak it that way, but I would keep going with the source if that’s what you want, and create a patch for if/when you upgrade.

G

From: Harkeerat Bedi [mailto:hsbedi-lg4TTeReta+Vc3sceRu5cw@public.gmane.org]
Sent: Tuesday, July 05, 2011 5:49 PM
To: iperf-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [Iperf-users] iPerf 2.0.5, add additional information in server output.