iperf3: error - unable to receive control message: Software caused connection abort

[ramir27]

NOTE: The iperf3 issue tracker is for registering bugs, enhancement
requests, or submissions of code. It is not a means for asking
questions about building or using iperf3. Those are best directed
towards the iperf3 mailing list at [email protected] or
question sites such as Stack Overflow
(http://www.stackoverflow.com/). A list of frequently-asked questions
regarding iperf3 can be found at http://software.es.net/iperf/faq.html.

Context

• Version of iperf3:

iperf 3.1.3

• Hardware:

PC -> Wireless router -> PC

• Operating system (and distribution, if any):

Windows 7 64bit

Please note: iperf3 is supported on Linux, FreeBSD, and macOS.
Support may be provided on a best-effort basis to other UNIX-like
platforms. We cannot provide support for building and/or running
iperf3 on Windows, iOS, or Android.

• Other relevant information (for example, non-default compilers,
  libraries, cross-compiling, etc.):

Please fill out one of the "Bug Report" or "Enhancement Request"
sections, as appropriate.

Bug Report

here is the log from the client:

iperf 3.1.3
CYGWIN_NT-6.1 DPNB 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Tue, 13 Feb 2018 08:31:14 GMT
Connecting to host 192.168.131.2, port 5003
Cookie: DPNB.1518510674.427355.0e00bfa6
[ 4] local 192.168.131.1 port 55076 connected to 192.168.131.2 port 5003
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 0 seconds, 20 second test
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.01 sec 456 KBytes 3684 Kbits/sec 57
[ 4] 1.01-2.01 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 2.01-3.01 sec 88.0 KBytes 722 Kbits/sec 11
[ 4] 3.01-4.01 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 4.01-5.01 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 5.01-6.01 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 6.01-7.00 sec 88.0 KBytes 722 Kbits/sec 11
[ 4] 7.00-8.00 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 8.00-9.00 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 9.00-10.02 sec 88.0 KBytes 711 Kbits/sec 11
[ 4] 10.02-11.01 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 11.01-12.01 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 12.01-13.01 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 13.01-14.01 sec 88.0 KBytes 722 Kbits/sec 11
[ 4] 14.01-15.01 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 15.01-16.01 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 16.01-17.00 sec 80.0 KBytes 656 Kbits/sec 10
[ 4] 17.00-18.00 sec 88.0 KBytes 722 Kbits/sec 11
[ 4] 18.00-19.00 sec 80.0 KBytes 656 Kbits/sec 10
iperf3: error - unable to receive control message: Software caused connection abort

• Expected Behavior

there is an error after sending UDP for 20 sec , it shouldent be.

• Actual Behavior

iperf3: error - unable to receive control message: Software caused connection abort

• Steps to Reproduce

server command: iperf3 -s -p 5003 k -V
client command: iperf3 -c 192.168.131.2 -u -i 1 -b 6M -4 -P 1 -t 20 -p 5003 -f k -V

• Possible Solution

Non

Please submit patches or code changes as a pull request.

Enhancement Request

• Current behavior

control packet may be lost stuck the client.

• Desired behavior

send another control packet . not stuck the client.

• Implementation notes

If submitting a proposed implementation of an enhancement request,
please use the pull request mechanism.

[bmah888]

Windows isn't an officially supported platform, but I believe that some of the newer versions of iperf3 do work better on Windows, if you can find an executable or have the ability to compile it yourself. Note that ESnet only distributes iperf3 in source code form.

Closing for now, there isn't really anything we can do about this.

[gobige]

cat /proc/version
Linux version 3.10.0-1062.12.1.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC) ) #1 SMP Tue Feb 4 23:02:59 UTC 2020

[root@ecs-pre-business-02 ~]# iperf3 -c ##.##.##.## -b 1G -t 15 -P 2 -p 10000
iperf3: error - received an unknown control message

This is my case, there is still no work on the linux platform。 IP is hidden by me

[cycy520]

I have same issue as you, when use iperf3 to run the throughput test, a disconnection will occur.
I have no idea on this, cause if I don't run iperf test, there won't any disconnection issue...
@gobige did you have fix this issue? Could you pls kindly share your experience?
Thanks a lot!

[StefanKaerst]

looks like there are two different versions of iperf server/client which cannot talk to each other. you have to use either iperf or iperf3 at the client and server.

skaerst@test06-debian10:~$ iperf -v
iperf version 2.0.12 (25 June 2018) pthreads

skaerst@test06-debian10:~$ iperf3 -v
iperf 3.6 (cJSON 1.5.2)
Linux test06-debian10 4.19.0-23-amd64 #1 SMP Debian 4.19.269-1 (2022-12-20) x86_64
Optional features available: CPU affinity setting, IPv6 flow label, SCTP, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication

HTH

[davidBar-On]

looks like there are two different versions of iperf server/client which cannot talk to each other. you have to use either iperf or iperf3 at the client and server.

@StefanKaerst, this is correct. iperf and iperf3 are two different programs and do not work with each other. See Relation to iperf 2.x in the iperf3 readme.