Hi guys,
I'm performing some local test on my network with iperf3 using UDP
connections between 2 Ubuntu 18.04 hosts. But it seems that the UDP iperf3
connections it is not robust to support a random packet drop of 0.1? When
executing the iperf3 tests, the server hangs (i need to restart the server
to allow connecting again) and I'm seeing this errors:
At the server:
*iperf3: the client has unexpectedly closed the connection*
At the client:
*error - unable to write to stream socket: Operation not permitted*
To simulate/test a bad hop on my network I'm using iptables to generate
random packet drops with this command (executed at the host A):
*sudo iptables -A OUTPUT -p udp -d HOSTB -m statistic --mode random
--probability 0.01 -j DROP*
And the iperf3 client executed at the host A:
*iperf3 --version4 --udp --client 10.0.3.10 --port 4000 --bind 10.0.1.10
--cport 12346 --json --zerocopy --verbose --bandwidth 300M --debug*
At the host B i'm using:
*iperf3 --verbose --server --port 4000 --version4 --debug*
As far as documentation/internet examples goes, iperf3 can work with very
bad networks, what can be happening here?
I have posted this question on ServerFault also:
https://serverfault.com/questions/926900/iperf3-udp-not-reliable-with-iptables-drop-random.
My iperf3 version is:
*iperf 3.1.3*
*Linux PC1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
x86_64*
*Optional features available: CPU affinity setting, IPv6 flow label, TCP
congestion algorithm setting, sendfile / zerocopy, socket pacing*
The problem also happens with iperf2.
Thanks!
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Iperf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/iperf-users
