>> Consider also that the nature of iperf is to saturate the available
channel.
This isn't the case anymore for iperf 2.0.13 and greater. Saturating the
channel has lots of negative effects with respect to testing per buffer
bloat. 2.0.13 and greater has many features to support unsaturated
chan
I can't speak for iperf 3 but iperf 2.0.13 supports -b on the server for
both TCP and UDP. It does this by running a simplified token bucket on the
reads(). With that said, there is no way for a server to control the
transmit rate of a iperf client running UDP because UDP is connectionless.
TCP is
Try to solve this need at network level by configuring QOS or COS or
interface speed.
That said, flooding the network with udp packets is possible even without
an iperf server on your side.
Consider also that the nature of iperf is to saturate the available channel.
Sandro
Il gio 3 ott 2019, 13:41
