Closed GoogleCodeExporter closed 9 years ago
That's not really what iperf is designed for. Supporting multiple tests at the
same time, while not hard, raises the possibility that the tests will interfere
with each other at the server. This is particularly true in the
high-performance networking environments for which iperf3 was designed. So by
design, we explicitly drop connection requests that come in while a test is
running.
I recommend we not address this enhancement.
Original comment by bmah@es.net
on 23 Dec 2013 at 5:01
Understood. Thank you for the clarification.
Original comment by alvinc...@gmail.com
on 23 Dec 2013 at 6:17
You can always use the iperf3 library and write you own application for this
use case if you'd like.
Original comment by bltier...@es.net
on 23 Dec 2013 at 11:11
Adding to the #3 you can always run the multiple instance of the server in
multiple ports
iperf3 -s -p 12345
Original comment by susant%redhat.com@gtempaccount.com
on 24 Dec 2013 at 4:15
Marking as WontFix, as this isn't really a part of iperf's design.
Original comment by bmah@es.net
on 2 Jan 2014 at 9:06
Original issue reported on code.google.com by
alvinc...@gmail.com
on 20 Dec 2013 at 11:28