search

esnet / iperf

iperf3: A TCP, UDP, and SCTP network bandwidth measurement tool
Other
6.91k stars 1.28k forks source link

iperf3: error - unable to send control message: Bad file descriptor #1150

Open zhongyong opened 3 years ago

zhongyong commented 3 years ago

iperf3 -c 192.168.189.167 -t 3 -p 5201 -l 16K -f M -P 3

TheRealDJ commented 3 years ago

What version?

bmah888 commented 3 years ago

Could we see the complete output from the client (and server if available)?

igo95862 commented 3 years ago

I also have this problem on Arch Linux:

iperf 3.9 (cJSON 1.7.13) Linux hostname 5.12.6-arch1-1 #1 SMP PREEMPT Sun, 23 May 2021 00:45:50 +0000 x86_64 Optional features available: CPU affinity setting, IPv6 flow label, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication

However, I have built an AUR git version it does not seems to have this error.

TheRealDJ commented 3 years ago

I also have this problem on Arch Linux:

iperf 3.9 (cJSON 1.7.13) Linux hostname 5.12.6-arch1-1 #1 SMP PREEMPT Sun, 23 May 2021 00:45:50 +0000 x86_64 Optional features available: CPU affinity setting, IPv6 flow label, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication

However, I have built an AUR git version it does not seems to have this error.

Can you provide client and server output showing the issue? Is the server running iperf 3.9 also?

boelle commented 2 months ago

i also have this error

on server:

root@omvnap:~# iperf3 -s -p 5100 -B 192.168.1.246 -V
iperf 3.9
Linux omvnap 6.1.0-0.deb11.13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1~bpo11+1 (2023-10-08) x86_64
-----------------------------------------------------------
Server listening on 5100
-----------------------------------------------------------

on client:

root@bo-omv:~# iperf3 -c **.2.xxx.181 -p 5100 --udp
iperf3: error - unable to send control message: Bad file descriptor

both are version 3.9... only port 5100 udp are open at the server end

Client:

iperf 3.9 (cJSON 1.7.13)
Linux bo-omv 6.1.0-0.deb11.17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1~bpo11+1 (2024-01-05) x86_64
Optional features available: CPU affinity setting, IPv6 flow label, SCTP, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication

Server:

iperf 3.9 (cJSON 1.7.13)
Linux omvnap 6.1.0-0.deb11.13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1~bpo11+1 (2023-10-08) x86_64
Optional features available: CPU affinity setting, IPv6 flow label, SCTP, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication
boelle commented 2 months ago

works fine if i also run the client on same box as the server

root@omvnap:~# iperf3 -c 192.168.1.246 -p 5100 --udp -R
Connecting to host 192.168.1.246, port 5100
Reverse mode, remote host 192.168.1.246 is sending
[  5] local 192.168.1.246 port 53224 connected to 192.168.1.246 port 5100
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-1.00   sec   160 KBytes  1.31 Mbits/sec  2.119 ms  0/5 (0%)
[  5]   1.00-2.00   sec   128 KBytes  1.05 Mbits/sec  1.649 ms  0/4 (0%)
[  5]   2.00-3.00   sec   128 KBytes  1.05 Mbits/sec  1.285 ms  0/4 (0%)
[  5]   3.00-4.00   sec   128 KBytes  1.05 Mbits/sec  1.005 ms  0/4 (0%)
[  5]   4.00-5.00   sec   128 KBytes  1.05 Mbits/sec  0.784 ms  0/4 (0%)
[  5]   5.00-6.00   sec   128 KBytes  1.05 Mbits/sec  0.609 ms  0/4 (0%)
^C[  5]   6.00-6.15   sec  0.00 Bytes  0.00 bits/sec  0.609 ms  0/0 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-6.15   sec  0.00 Bytes  0.00 bits/sec  0.000 ms  0/0 (0%)  sender
[  5]   0.00-6.15   sec   800 KBytes  1.06 Mbits/sec  0.609 ms  0/25 (0%)  receiver
iperf3: interrupt - the client has terminated

also works with public servers, so yeah will double check my router settings as something is blocking it

bmah888 commented 2 months ago

works fine if i also run the client on same box as the server

root@omvnap:~# iperf3 -c 192.168.1.246 -p 5100 --udp -R
Connecting to host 192.168.1.246, port 5100
Reverse mode, remote host 192.168.1.246 is sending
[  5] local 192.168.1.246 port 53224 connected to 192.168.1.246 port 5100
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-1.00   sec   160 KBytes  1.31 Mbits/sec  2.119 ms  0/5 (0%)
[  5]   1.00-2.00   sec   128 KBytes  1.05 Mbits/sec  1.649 ms  0/4 (0%)
[  5]   2.00-3.00   sec   128 KBytes  1.05 Mbits/sec  1.285 ms  0/4 (0%)
[  5]   3.00-4.00   sec   128 KBytes  1.05 Mbits/sec  1.005 ms  0/4 (0%)
[  5]   4.00-5.00   sec   128 KBytes  1.05 Mbits/sec  0.784 ms  0/4 (0%)
[  5]   5.00-6.00   sec   128 KBytes  1.05 Mbits/sec  0.609 ms  0/4 (0%)
^C[  5]   6.00-6.15   sec  0.00 Bytes  0.00 bits/sec  0.609 ms  0/0 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-6.15   sec  0.00 Bytes  0.00 bits/sec  0.000 ms  0/0 (0%)  sender
[  5]   0.00-6.15   sec   800 KBytes  1.06 Mbits/sec  0.609 ms  0/25 (0%)  receiver
iperf3: interrupt - the client has terminated

also works with public servers, so yeah will double check my router settings as something is blocking it

You also need to allow TCP on port 5100 as well for the iperf3 control connection.