Replies: 1 comment 1 reply
-
iperf3 (unlike a number of other utilities) uses a control connection, which runs over TCP, to exchange data between the client and server before the start of the actual data transfer. The socket you are seeing on the server is listening for the client to make the initial TCP control connection. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear Team,
from iperf3 onwards, we should just mentioned "iperf3 -s" to listen on default port of 5201.
netstat shows that server is listening on tcp6.
Please help me understand how are we handling UDP client packets, when server socket is of type stream.
Any basic pointers from code perspective is appreciated.
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp6 0 0 :::5201 :::* LISTEN 12743/iperf3
root@pidda:/home/pidda/Documents/MyPHD/containernet/examples#
Beta Was this translation helpful? Give feedback.
All reactions