-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iperf3: error - control socket has closed unexpectedly #1803
Comments
Are you running also an iperf3 server? iperf2 and iperf3 are not compatible, so each should use its own server. If this is not the problem, do you have an output from the server? That might help to understand what the problem is. Another reason may be related to ports that are closed in the firewall (but per the error I don't think this is the reason). |
Are you running also an iperf3 server? iperf2 and iperf3 are not compatible, so each should use its own server. If this is not the problem, do you have an output from the server? That might help to understand what the problem is. Another reason may be related to ports that are closed in the firewall. Can you also show the iperf2 command you used successfully? |
No, I don't use a iperf3-server? I have a problem with the speed from the Linux-PC to the NAS (Nfs4). So I was looking for iperf to measure the speed. The iperf2 command is the last one above in my first post. I have this server-output (192.168.0.2 is the Linux-PC): Nov 27 08:04:36 xigmanas64fu lighttpd: (h1.c.413) oversized request-header -> sending Status 431 |
These ports are open at 192.168.0.43 (NAS): Port Status Dienst |
As I wrote, you cannot use ipef3 client with iperf (iperf2) server. Since you are using iperf server, and as you wrote the iperf test is successful, I am not sure what is the problem. I the problem is that you want to use iperf3 instead, you must run iperf3 server. |
I don't understand you. I have only both iperf-versions installed on my PC from which I try to measure the conncection to the NAS. I don't know anything about iperf-server. I think I am missing something to know...? :-) |
iperf (all versions) are testing the connection throughput, etc. using client-server interface. In your case, iperf server is running on 192.168.0.43 machine and is using port 2049. Since 192.168.x.x is a local address, I assume you can find the machine and what is running on it. To understand this better, try the following in your PC:
You should see the test results output from both the client and the server. Note that the default port used is 5201. If there is a problem with this port, you can try using another port using the |
Awesome! Thank you! First I did it with success on the PC with 2 terminals open. I found that on den XigmaNAS iperf3 is still installed! I didn't know this. Now I did this: In the server terminal: iperf3 -s I got an answer and a middle Bitrate about 50 Mbits/sec. Do I right now? This Bitrate is still low. But it is not on iperf3... |
Looks good! |
Thank you very much! |
Using iperf (v2) I get a correct answer about a slow connection in a 1GBit/s network from Manjaro to Xigmanas (NFS).
iperf 2.2.0-1
iperf 3.17.1
System: Kernel: 6.6.54-2-MANJARO arch: x86_64 bits Desktop: GNOME v: 46.5 tk: GTK v: 3.24.43 wm: gnome-shell
Complete System attached:
System_complete.txt
I tried several settings, but could not go out of the iperf3 error:
[tom@tom-manjaro ~]$ iperf3 -c 192.168.0.43 -p 2049 iperf3: error - control socket has closed unexpectedly
[tom@tom-manjaro ~]$ iperf3 -c 192.168.0.43 -p 2049 -V iperf 3.17.1 Linux tom-manjaro 6.6.54-2-MANJARO #1 SMP PREEMPT_DYNAMIC Tue Oct 8 03:11:08 UTC 2024 x86_64 Control connection MSS 1448 iperf3: error - control socket has closed unexpectedly
[tom@tom-manjaro ~]$ iperf -c 192.168.0.43 -p 2049 Client connecting to 192.168.0.43, TCP port 2049 TCP window size: 16.0 KByte (default) [ 1] local 192.168.0.2 port 48904 connected with 192.168.0.43 port 2049 [ ID] Interval Transfer Bandwidth [ 1] 0.0000-16.7145 sec 22.5 MBytes 11.3 Mbits/sec
Any idea?
The text was updated successfully, but these errors were encountered: