Hi All,
I've added a few more options to the iperf 2 bounceback test around responsiveness & working load.
CLIENT SPECIFIC OPTIONS
--bounceback
run a tcp bounceback test (set size with -l or --len, defaults to 100 bytes)
--bounceback-congest[=up|down|bidir][,n]
request a concurrent working load or TCP stream(s), defaults to full duplex (or bidir) unless the up or down option is provided. The number of TCP streams defaults to 1 and
can be changed via the n value, e.g. --bounceback-congest=down,4 will use four TCP streams from server to the client as the working load. The IP ToS will be BE (0x0) for
working load traffic.
Also, thanks to Dave and some WMM QoS guys, I've added symbolic names to the --tos and --tos-override support.
IP tos: Specifies the type-of-service or DSCP class for connections. Accepted values are af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs0, cs1, cs2,
cs3, cs4, cs5, cs6, cs7, ef, le, nqb, nqb2, ac_be, ac_bk, ac_vi, ac_vo, lowdelay, throughput, reliability, a numeric value, or none to use the operating system default. The ac_xx
values are the four access categories defined in WMM for Wi-Fi, and they are aliases for DSCP values that will be mapped to the corresponding ACs under the assumption that the de‐
vice uses the DSCP-to-UP mapping table specified in IETF RFC 8325.
Thanks,
Bob