Client reports wrong speed since 7065f57
A means to measure network responsiveness and throughput
Brought to you by:
rjmcmahon
Since 7065f57 the client reports random garbage speed, see below.
Maybe this is due to the use of a high speed link? Everything else on this machine is quite the default, Ubuntu 20.04 LTS.
With 7065f57:
src/iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 128 KByte (default)
------------------------------------------------------------
[ 1] local 10.100.1.1 port 5001 connected with 10.100.1.2 port 40698 (icwnd/mss/irtt=14/1448/59)
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-2.00 sec 5.44 GBytes 23.3 Gbits/sec
iperf -c 10.100.1.1 -t 2[13:22:31]
------------------------------------------------------------
Client connecting to 10.100.1.1, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[ 1] local 10.100.1.2 port 40698 connected with 10.100.1.1 port 5001 (icwnd/mss/irtt=14/1448/187)
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-2.01 sec 60.0 Bytes 238 bits/sec
The expected behavior with 7065f57~2 (~1 is creating problems):
src/iperf -c 10.100.1.1 -t 2
------------------------------------------------------------
Client connecting to 10.100.1.1, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[ 1] local 10.100.1.2 port 40704 connected with 10.100.1.1 port 5001 (icwnd/mss/irtt=14/1448/262)
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-2.01 sec 5.59 GBytes 23.9 Gbits/sec
grincheux (1) [1578] % /etinfo/users2/tbarbette/workspace/npf/build/iperf2-git/src/iperf -c 10.100.1.1 -t 2
Note that the server is reporting the correct speed.
I haven't reproduced this. Can you provide the output of iperf -v?
~2 :
iperf version 2.1.n (18 April 2023) pthreads
7065f57:
iperf version 2.1.n (20 April 2023) pthreads
Fixed here. Use -e for a work around on previous versions.