Oh, you can do this, just don't sue the -p switch when using tcp on the server, its iperf -s <tcp_port> .....
I did'nt understand this until I looked at the error messages for a long time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
Oh, you can do this, just don't sue the -p switch when using tcp on the server, its iperf -s <tcp_port> .....
I did'nt understand this until I looked at the error messages for a long time.
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
SOLVED
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
NO, that's not quite right either, I was mistaken using -t to try and get TCP. Correct syntax is "iperf -s -p 1720 ....".
Sorry for all the confusion - caffeine must be wearing off.