iperf-2.0.14a-Nov30 -r and -d doesn't work
A means to measure network responsiveness and throughput
Brought to you by:
rjmcmahon
iperf-2.0.14a-Nov30 (both windows and linux, TCP and UDP tests) -r and -d doesn't work
communication between tested machines is ok:
Server: 192.168.77.46 :
iperf-2.0.14a-Nov30-win.exe -s -w2M
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 2.00 MByte
------------------------------------------------------------
[ 1] local 192.168.77.46 port 5001 connected with 192.168.77.12 port 52626
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-10.00 sec 1.10 GBytes 942 Mbits/sec
Client: 192.168.77.12 :
iperf-2.0.14a-Nov30-win.exe -c 192.168.77.46 -w2M
------------------------------------------------------------
Client connecting to 192.168.77.46, TCP port 5001
TCP window size: 2.00 MByte
------------------------------------------------------------
[ 1] local 192.168.77.12 port 52626 connected with 192.168.77.46 port 5001
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-10.00 sec 1.10 GBytes 942 Mbits/sec
Server: 192.168.77.12 :
iperf-2.0.14a-Nov30-win.exe -s -w2M
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 2.00 MByte
------------------------------------------------------------
[ 1] local 192.168.77.12 port 5001 connected with 192.168.77.46 port 49714
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-10.01 sec 615 MBytes 515 Mbits/sec
Client: 192.168.77.46 :
iperf-2.0.14a-Nov30-win.exe -c 192.168.77.12 -w2M
------------------------------------------------------------
Client connecting to 192.168.77.12, TCP port 5001
TCP window size: 2.00 MByte
------------------------------------------------------------
[ 1] local 192.168.77.46 port 49714 connected with 192.168.77.12 port 5001
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-10.01 sec 615 MBytes 515 Mbits/sec
But:
iperf-2.0.14a-Nov30-win.exe -s -w2M
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 2.00 MByte
------------------------------------------------------------
[ 1] local 192.168.77.46 port 5001 connected with 192.168.77.12 port 52686
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-9.98 sec 1.10 GBytes 944 Mbits/sec
tcp connect failed: Connection timed out.
iperf-2.0.14a-Nov30-win.exe -c 192.168.77.46 -w2M -d
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 2.00 MByte
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.77.46, TCP port 5001
TCP window size: 2.00 MByte
------------------------------------------------------------
[ 1] local 192.168.77.12 port 52686 connected with 192.168.77.46 port 5001
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-10.00 sec 1.10 GBytes 942 Mbits/sec
ERROR: expected reverse connect did not occur
same with -r
iperf-2.0.14a-Nov30-win.exe -s -w2M
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 2.00 MByte
------------------------------------------------------------
[ 1] local 192.168.77.46 port 5001 connected with 192.168.77.12 port 52733
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-10.00 sec 1.10 GBytes 942 Mbits/sec
tcp connect failed: Connection timed out.
iperf-2.0.14a-Nov30-win.exe -c 192.168.77.46 -w2M -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 2.00 MByte
------------------------------------------------------------
------------------------------------------------------------
Client connecting to 192.168.77.46, TCP port 5001
TCP window size: 2.00 MByte
------------------------------------------------------------
[ 1] local 192.168.77.12 port 52733 connected with 192.168.77.46 port 5001
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-10.00 sec 1.10 GBytes 942 Mbits/sec
ERROR: expected reverse connect did not occur
Tested between 2 Windows, 2 Linux machines and between Windows and Linux
Can you try with --full-duplex too?
Thanks,
Bob
--full-duplex works ok
I haven't been able to reproduct this so far. Does --reverse also work? Do older versions, e..g. iperf 2.0.13, work? It shows like a firewall problem but could be something else.
Ok, I reproduced it. I'll debug tomorrow PST
Ok, should be fixed. this was a regression. Thanks for finding it
Bob