Description: fix hyphen used as minus sign in manpages and line break
 this is merged 003 and 004
Author: Roberto Lumbreras <rover@debian.org>
Author: PICCORO Lenz McKAY <mckaygerhard@gmail.com>

--- iperf-2.1.0-rc2.orig/man/iperf.1
+++ iperf-2.1.0-rc2/man/iperf.1
@@ -2,13 +2,13 @@
 .SH NAME
 iperf \- perform network traffic tests using network sockets. Metrics include throughput and latency.
 .SH SYNOPSIS
-.BI "iperf -s [" options ]
+.BI "iperf \-s [" options ]
 
-.BI "iperf -c " server " [" options ]
+.BI "iperf \-c " server " [" options ]
 
-.BI "iperf -u -s [" options ]
+.BI "iperf \-u \-s [" options ]
 
-.BI "iperf -u -c "  server " [" options ]
+.BI "iperf \-u \-c "  server " [" options ]
 
 .SH DESCRIPTION
 .LP
@@ -17,7 +17,7 @@ metrics supported include throughput and
 protocols.) It supports unidirectional, full duplex (same socket) and bidirectional traffic, and supports
 multiple, simultaneous traffic streams. It supports multicast traffic including source specific
 multicast (SSM) joins. Its multi-threaded design allows for peak performance. Metrics displayed help to
-characterize host to host network performance. Note: Setting the enhanced (-e) option provides all
+characterize host to host network performance. Note: Setting the enhanced (\-e) option provides all
 available metrics.
 .LP
 The user must establish both a both a server (to receive traffic)
@@ -26,225 +26,222 @@ The client and server typically are on d
 computers but need not be.
 .SH "GENERAL OPTIONS"
 .TP
-.BR -b ", " --bandwidth " "
+.BR \-b ", " \-\-bandwidth " "
 set the target bandwidth and optional standard deviation per
 \fI<mean>\fR,\fI[<stdev>]\fR (See NOTES for suffixes)
 .TP
-.BR -e ", " --enhanced " "
+.BR \-e ", " \-\-enhanced " "
 Display enhanced output in reports otherwise use legacy report (ver
 2.0.5) formatting (see notes)
 .TP
-.BR -f ", " --format " " [abkmgBKMG]
+.BR \-f ", " \-\-format " " [abkmgBKMG]
 format to report: adaptive, bits, Bytes, Kbits, Mbits, Gbits, KBytes,
 MBytes, GBytes (see NOTES for more)
 .TP
-.BR -h ", " --help " "
+.BR \-h ", " \-\-help " "
 print a help synopsis
 .TP
-.BR -i ", " --interval " < \fIn\fR[p] | f >"
-sample or display interval reports every \fIn\fR seconds (default) or \fIn\fR packets (per optional p suffix.) If f is used then the interval will be each frame or burst. The frame interval reporting is experimental.  Also suggest a compile with fast-sampling, i.e. ./configure --enable-fastsampling
+.BR \-i ", " \-\-interval " < \fIn\fR[p] | f >"
+sample or display interval reports every \fIn\fR seconds (default) or \fIn\fR packets (per optional p suffix.) If f is used then the interval will be each frame or burst. The frame interval reporting is experimental.  Also suggest a compile with fast-sampling, i.e. ./configure \-\-enable\-fastsampling
 .TP
-.BR -l ", " --len " \fIn\fR[kmKM]"
+.BR \-l ", " \-\-len " \fIn\fR[kmKM]"
 set read/write buffer size (TCP) or length (UDP) to \fIn\fR (TCP default 128K, UDP default 1470)
 .TP
-.BR "    --l2checks "
+.BR "    \-\-l2checks "
 perform layer 2 length checks on received UDP packets (requires systems that support packet sockets, e.g. Linux)
 .TP
-.BR -m ", " --print_mss " "
+.BR \-m ", " \-\-print_mss " "
 print TCP maximum segment size (MTU - TCP/IP header)
 .TP
-.BR "    --NUM_REPORT_STRUCTS " \fI<count>\fR
+.BR "    \-\-NUM_REPORT_STRUCTS " \fI<count>\fR
 Override the default shared memory size between the traffic thread(s) and reporter thread in order to mitigate mutex lock contentions. The default value of 5000 should be sufficient for 1Gb/s networks. Increase this upon seeing the Warning message of reporter thread too slow. If the Warning message isn't seen, then increasing this won't have any significant effect (other than to use some additional memory.)
 .TP
-.BR -o ", " --output " \fIfilename\fR"
+.BR \-o ", " \-\-output " \fIfilename\fR"
 output the report or error message to this specified file
 .TP
-.BR "    --permit-key [=" \fI<value>\fR "]"
+.BR "    \-\-permit-key [=" \fI<value>\fR "]"
 Set a key value that must match for the server to accept traffic on a connection. If the option is given without a value on the server a key value will be autogenerated and displayed in its initial settings report. The value is required on clients. The value will also be used as part of the transfer id in reports. The option set on the client but not the server will also cause the server to reject the client's traffic. TCP only, no UDP support.  (suggested is to use with -1 or --single-client, -P 1 on the server, and -t on the server which is very short)
 .TP
-.BR -p ", " --port " \fIn\fR"
+.BR \-p ", " \-\-port " \fIn\fR"
 set server port to listen on/connect to to \fIn\fR (default 5001)
 .TP
-.BR "    --sum-only "
-set the output to sum reports only. Useful for -P at large values
+.BR "    \-\-sum\-only "
+set the output to sum reports only. Useful for \-P at large values
 .TP
-.BR -u ", " --udp " "
+.BR \-u ", " \-\-udp " "
 use UDP rather than TCP
 .TP
-.BR -w ", " --window " \fIn\fR[kmKM]"
+.BR \-w ", " \-\-window " \fIn\fR[kmKM]"
 TCP window size (socket buffer size)
 .TP
-.BR -z ", " --realtime " "
-Request real-time scheduler, if supported.
+.BR \-z ", " \-\-realtime " "
+Request real\-time scheduler, if supported.
 .TP
-.BR -B ", " --bind " \fIhost\fR[:\fIport\fR][%\fIdev\fR]"
+.BR \-B ", " \-\-bind " \fIhost\fR[:\fIport\fR][%\fIdev\fR]"
 bind to \fIhost\fR, ip address or multicast address, optional port or device (see NOTES)
 .TP
-.BR -C ", " --compatibility " "
+.BR \-C ", " \-\-compatibility " "
 for use with older versions does not sent extra msgs
 .TP
-.BR -M ", " --mss " \fIn\fR"
+.BR \-M ", " \-\-mss " \fIn\fR"
 set TCP maximum segment size (MTU - 40 bytes)
 .TP
-.BR -N ", " --nodelay " "
+.BR \-N ", " \-\-nodelay " "
 set TCP no delay, disabling Nagle's Algorithm
 .TP
-.BR -v ", " --version " "
+.BR \-v ", " \-\-version " "
 print version information and quit
 .TP
-.BR -x ", " --reportexclude " [CDMSV]"
+.BR \-x ", " \-\-reportexclude " [CDMSV]"
 exclude C(connection) D(data) M(multicast) S(settings) V(server) reports
 .TP
-.BR -y ", " --reportstyle " C|c"
+.BR \-y ", " \-\-reportstyle " C|c"
 if set to C or c report results as CSV (comma separated values)
 .TP
-.BR -Z ", " --tcp-congestion " "
-Set the default congestion-control algorithm to be used for new connections. Platforms must support setsockopt's TCP_CONGESTION. (Notes: See sysctl and tcp_allowed_congestion_control for available options. May require root privileges.)
+.BR \-Z ", " \-\-tcp\-congestion " "
+Set the default congestion\-control algorithm to be used for new connections. Platforms must support setsockopt's TCP_CONGESTION. (Notes: See sysctl and tcp_allowed_congestion_control for available options. May require root privileges.)
 .SH "SERVER SPECIFIC OPTIONS"
 .TP
-.BR -1 ", " --singleclient " "
+.BR \-1 ", " \-\-singleclient " "
 set the server to process only one client at a time
 .TP
-.BR -b ", " --bandwidth " \fIn\fR[kmgKMG]"
+.BR \-b ", " \-\-bandwidth " \fIn\fR[kmgKMG]"
 set target read rate to \fIn\fR bits/sec. TCP only for the server.
 .TP
-.BR -s ", " --server " "
+.BR \-s ", " \-\-server " "
 run in server mode
 .TP
-.BR "    --histograms[="\fIbinwidth\fR[u],\fIbincount\fR,[\fIlowerci\fR],[\fIupperci\fR] "]"
-enable latency histograms for udp packets (-u), for tcp writes (with --trip-times), or for either udp or tcp with --isochronous clients. The binning can be modified. Bin widths (default 1 millisecond, append u for microseconds,) bincount is total bins (default 1000), ci is confidence interval between 0-100% (default lower 5%, upper 95%, 3 stdev 99.7%)
+.BR "    \-\-histograms[="\fIbinwidth\fR[u],\fIbincount\fR,[\fIlowerci\fR],[\fIupperci\fR] "]"
+enable latency histograms for udp packets (-u), for tcp writes (with \-\-trip\-times), or for either udp or tcp with \-\-isochronous clients. The binning can be modified. Bin widths (default 1 millisecond, append u for microseconds,) bincount is total bins (default 1000), ci is confidence interval between 0-100% (default lower 5%, upper 95%, 3 stdev 99.7%)
 .TP
-.BR -B ", " --bind " \fIip\fR | \fIip\fR%\fIdevice\fR"
+.BR \-B ", " \-\-bind " \fIip\fR | \fIip\fR%\fIdevice\fR"
 bind src ip addr and optional src device for receiving
 .TP
-.BR -D ", " --daemon " "
+.BR \-D ", " \-\-daemon " "
 run the server as a daemon. On Windows this will run the specified
 command-line under the IPerfService, installing the service if
 necessary. Note the service is not configured to auto-start or
 restart - if you need a self-starting service you will need to create
 an init script or use Windows "sc" commands.
 .TP
-.BR -H ", " --ssm-host " \fIhost\fR"
+.BR \-H ", " \-\-ssm\-host " \fIhost\fR"
 Set the source host (ip addr) per SSM multicast, i.e. the S of the S,G
 .TP
-.BR -R ", " --remove " "
+.BR \-R ", " \-\-remove " "
 remove the IPerfService (Windows only).
 .TP
-.BR -U ", " --single_udp " "
+.BR \-U ", " \-\-single_udp " "
 run in single threaded UDP mode
 .TP
-.BR -V ", " --ipv6_domain " "
+.BR \-V ", " \-\-ipv6_domain " "
 Enable IPv6 reception by setting the domain and socket to AF_INET6 (Can receive on both IPv4 and IPv6)
 .SH "CLIENT SPECIFIC OPTIONS"
 .TP
-.BR -b ", " --bandwidth " \fIn\fR[kmgKMG][,\fIn\fR[kmgKMG]] | \fIn\fR\fR[kmgKMG]pps"
+.BR \-b ", " \-\-bandwidth " \fIn\fR[kmgKMG][,\fIn\fR[kmgKMG]] | \fIn\fR\fR[kmgKMG]pps"
 set target bandwidth to \fIn\fR bits/sec (default 1 Mbit/sec) or
 \fIn\fR packets per sec. This may be used with TCP or UDP. Optionally, for variable loads, use format of  mean,standard deviation
 .TP
-.BR -c ", " --client " \fI\fIhost\fR | \fIhost\fR%\fIdevice\fR"
+.BR \-c ", " \-\-client " \fI\fIhost\fR | \fIhost\fR%\fIdevice\fR"
 run in client mode, connecting to \fIhost\fR  where the optional %dev will SO_BINDTODEVICE that output interface (requires root and see NOTES)
 .TP
-.BR "    --connect-only[=" \fIn\fR "]"
+.BR "    \-\-connect\-only[=" \fIn\fR "]"
 only perform a TCP connect (or 3WHS) without any data transfer, useful to measure TCP connect() times. Optional value of n is the total number of connects to do (zero is run forever.) Note that -i will rate limit the connects where -P will create bursts and -t will end the client and hence end its connect attempts.
 .TP
-.BR "    --connect-retries " \fIn\fR "]"
+.BR "    \-\-connect\-retries " \fIn\fR "]"
 number of times to retry a TCP connect at the application level.  See operating system information on the details of TCP connect related settings.
 .TP
-.BR -d ", " --dualtest " "
+.BR \-d ", " \-\-dualtest " "
 Do a bidirectional test simultaneous test using two unidirectional sockets
 .TP
-.BR "    --fq-rate n[kmgKMG]"
+.BR "    \-\-fq\-rate n[kmgKMG]"
 Set a rate to be used with fair-queueing based socket-level pacing, in bytes or bits per second. Only available on platforms supporting the SO_MAX_PACING_RATE socket option. (Note: Here the suffixes indicate bytes/sec or bits/sec per use of uppercase or lowercase, respectively)
 .TP
-.BR "    --full-duplex"
+.BR "    \-\-full\-duplex"
 run a full duplex test, i.e. traffic in both transmit and receive directions using the \fBsame socket\fR
 .TP
-.BR "    --incr-dstip"
+.BR "    \-\-incr\-dstip"
 increment the destination ip address when using the parallel (-P) option
 .TP
-.BR "    --ipg "\fIn\fR
-set the inter-packet gap to \fIn\fR (units of seconds) for packets or within a frame/burst when --isochronous is set
+.BR "    \-\-ipg "\fIn\fR
+set the interpacket gap to \fIn\fR (units of seconds) for packets or within a frame/burst when \-\-isochronous is set
 .TP
-.BR "    --isochronous[=" \fIfps\fR:\fImean\fR,\fIstdev\fR "]"
+.BR "    \-\-isochronous[=" \fIfps\fR:\fImean\fR,\fIstdev\fR "]"
 send isochronous traffic with frequency frames per second and load defined by mean and standard deviation using a log normal distribution, defaults to 60:20m,0. (Note: Here the suffixes indicate bytes/sec or bits/sec per use of uppercase or lowercase, respectively. Also the p suffix is supported to set the burst size in packets, e.g. isochronous=2:25p will send two 25 packet bursts every second, or one 25 packet burst every 0.5 seconds.)
 .TP
-.BR "    --local-only[=\fI1\fR|\fI0\fR]"
-Set 1 to limit traffic to the local network only (through the use of SO_DONTROUTE) set to zero otherwise with optional override of compile time default (see configure --default-localonly)
+.BR "    \-\-local\-only[=\fI1\fR|\fI0\fR]"
+Set 1 to limit traffic to the local network only (through the use of SO_DONTROUTE) set to zero otherwise with optional override of compile time default (see configure \-\-default-localonly)
 .TP
-.BR "    --near-congestion[=\fIn\fR]"
-Enable TCP write rate limiting per the sampled RTT. The delay is applied after the -l number of bytes have completed. The optional value is the multiplier to the RTT and defines the time delay. This value defaults to 0.5 if it is not set. Values less than 1 are supported but the value cannot be negative. This is an experimental feature. It is not likely stable on live networks. Suggested use is over controlled test networks. Requires --trip-times.
+.BR "    \-\-near\-congestion[=\fIn\fR]"
+Enable TCP write rate limiting per the sampled RTT. The delay is applied after the -l number of bytes have completed. The optional value is the multiplier to the RTT and defines the time delay. This value defaults to 0.5 if it is not set. Values less than 1 are supported but the value cannot be negative. This is an experimental feature. It is not likely stable on live networks. Suggested use is over controlled test networks. Requires \-\-trip-times.
 .TP
 .TP
-.BR "    --no-connect-sync "
-By default, parallel traffic threads (per -P greater than 1) will synchronize after their TCP connects and prior to each sending traffic, i.e. all the threads first complete (or error) the TCP 3WHS before any traffic thread will start sending. This option disables that synchronization such that each traffic thread will start sending immediately after completing its successful connect.
+.BR "    \-\-no\-connect\-sync "
+By default, parallel traffic threads (per \-P greater than 1) will synchronize after their TCP connects and prior to each sending traffic, i.e. all the threads first complete (or error) the TCP 3WHS before any traffic thread will start sending. This option disables that synchronization such that each traffic thread will start sending immediately after completing its successful connect.
 .TP
-.BR "    --no-udp-fin "
+.BR "    \-\-no\-udp\-fin "
 Don't perform the UDP final server to client exchange which means there won't be a final server report displayed on the client. All packets per the test will be from the client to the server and no packets should be sent in the other direction.
-.B It's highly suggested that -t be set on the server if this option is being used.
+.B It's highly suggested that \-t be set on the server if this option is being used.
 This is because there will be
 .B only one trigger ending packet
 sent from client to server and if it's lost then the server will continue to run. (Requires ver 2.0.14 or better)
 .TP
-.BR -n ", " --num " \fIn\fR[kmKM]"
-number of bytes to transmit (instead of -t)
+.BR \-n ", " \-\-num " \fIn\fR[kmKM]"
+number of bytes to transmit (instead of \-t)
 .TP
-.BR "    --permit-key-timeout " \fI<value>\fR
-Set the lifetime of the permit key in seconds. Defaults to 20 seconds if not set. A value of zero will disable the timer.
-.TP
-.BR -r ", " --tradeoff " "
+.BR \-r ", " \-\-tradeoff " "
 Do a bidirectional test individually - client-to-server, followed by
 a reversed test, server-to-client
 .TP
-.BR -t ", " --time " \fIn\fR"
+.BR \-t ", " \-\-time " \fIn\fR"
 time in seconds to listen for new traffic connections, receive traffic or transmit traffic (Defaults: transmit is 10 secs while listen and receive are indefinite)
 .TP
-.BR "    --trip-times "
+.BR "    \-\-trip\-times "
 enable the measurement of end to end write to read latencies (client and server clocks must be synchronized)
 .TP
-.BR "    --txdelay-time "
+.BR "    \-\-txdelay\-time "
 time in seconds to hold back or delay after the TCP connect and prior to the socket writes. For UDP it's the delay between the traffic thread starting and the first write.
 .TP
-.BR "    --txstart-time "\fIn\fR.\fIn\fR
-set the txstart-time to \fIn\fR.\fIn\fR using unix or epoch time format (supports microsecond resolution, e.g 1536014418.123456) An example to delay one second using command substitution is iperf -c 192.168.1.10 --txstart-time $(expr $(date +%s) + 1).$(date +%N)
+.BR "    \-\-txstart\-time "\fIn\fR.\fIn\fR
+set the txstart\-time to \fIn\fR.\fIn\fR using unix or epoch time format (supports microsecond resolution, e.g 1536014418.123456) An example to delay one second using command subsitution is iperf \-c 192.168.1.10 \-\-txstart\-time $(expr $(date +%s) + 1).$(date +%N)
 .TP
-.BR -B ", " --bind " \fIip\fR | \fIip\fR:\fIport\fR | \fIipv6 -V\fR | \fI[ipv6]\fR:\fIport -V\fR"
+.BR \-B ", " \-\-bind " \fIip\fR | \fIip\fR:\fIport\fR | \fIipv6 \-V\fR | \fI[ipv6]\fR:\fIport \-V\fR"
 bind src ip addr and optional port as the source of traffic (see notes)
 .TP
-.BR -F ", " --fileinput " \fIname\fR"
+.BR \-F ", " \-\-fileinput " \fIname\fR"
 input the data to be transmitted from a file
 .TP
-.BR -I ", " --stdin " "
+.BR \-I ", " \-\-stdin " "
 input the data to be transmitted from stdin
 .TP
-.BR -L ", " --listenport " \fIn\fR"
+.BR \-L ", " \-\-listenport " \fIn\fR"
 port to receive bidirectional tests back on
 .TP
-.BR -P ", " --parallel " \fIn\fR"
+.BR \-P ", " \-\-parallel " \fIn\fR"
 number of parallel client threads to run
 .TP
-.BR -R ", " --reverse " "
+.BR \-R ", " \-\-reverse " "
 reverse the traffic flow (useful for testing through firewalls, see NOTES)
 .TP
-.BR -S ", " --tos " "
+.BR \-S ", " \-\-tos " "
 set the socket's IP_TOS (byte) field
 .TP
-.BR -T ", " --ttl " \fIn\fR"
+.BR \-T ", " \-\-ttl " \fIn\fR"
 time-to-live, for multicast (default 1)
-.BR -V ", " --ipv6_domain " "
+.BR \-V ", " \-\-ipv6_domain " "
 Set the domain to IPv6 (send packets over IPv6)
 .TP
-.BR -X ", " --peerdetect " "
+.BR \-X ", " \-\-peerdetect " "
 run peer version detection prior to traffic.
 .TP
-.BR -Z ", " --linux-congestion " \fIalgo\fR"
+.BR \-Z ", " \-\-linux\-congestion " \fIalgo\fR"
 set TCP congestion control algorithm (Linux only)
 .SH EXAMPLES
 
 .B TCP tests (client)
 
-.B iperf -c <host> -e -i 1
+.B iperf \-c <host> \-e \-i 1
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 Client connecting to <host>, TCP port 5001 with pid 5149
 .br
@@ -252,7 +249,7 @@ Write buffer size:  128 KByte
 .br
 TCP window size:  340 KByte (default)
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 [  3] local 45.56.85.133 port 49960 connected with 45.33.58.123 port 5001 (ct=3.23 ms)
 .br
@@ -281,7 +278,7 @@ TCP window size:  340 KByte (default)
 [  3] 0.00-10.00 sec  1.25 GBytes  1.07 Gbits/sec  10251/0       1196       -1K/3170 us  42382.03
 
 .TP
-.B where (per -e,)
+.B where (per \-e,)
 .B ct=
 TCP connect time (or three way handshake time 3WHS)
 .br
@@ -302,9 +299,9 @@ Network power defined as (throughput / R
 .B TCP tests (server)
 
 .B
-iperf -s -e -i 1 -l 8K
+iperf \-s \-e \-i 1 \-l 8K
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 Server listening on TCP port 5001 with pid 13430
 .br
@@ -312,7 +309,7 @@ Read buffer size: 8.00 KByte
 .br
 TCP window size: 85.3 KByte (default)
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 [  4] local 45.33.58.123 port 5001 connected with 45.56.85.133 port 49960
 .br
@@ -341,7 +338,7 @@ TCP window size: 85.3 KByte (default)
 [  4] 0.00-10.02 sec  1.25 GBytes  1.07 Gbits/sec  227306    9316:22088:21792:7096:22893:17193:6138:120790
 .br
 .TP
-.B where (per -e,)
+.B where (per \-e,)
 .B Reads
 Total number of socket reads
 .br
@@ -352,17 +349,17 @@ example, the bins are 0-1K, 1K-2K, .., 7
 
 .PP
 
-.B TCP tests (server with --trip-times on client)
+.B TCP tests (server with \-\-trip\-times on client)
 .B
-iperf -s -i 1 -w 4M
+iperf \-s \-i 1 \-w 4M
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 Server listening on TCP port 5001
 .br
 TCP window size: 8.00 MByte (WARNING: requested 4.00 MByte)
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 [  4] local 192.168.1.4%eth0 port 5001 connected with 192.168.1.7 port 44798 (trip-times) (MSS=1448) (peer 2.0.14-alpha)
 .br
@@ -392,7 +389,7 @@ TCP window size: 8.00 MByte (WARNING: re
 .br
 [  4] 0.00-10.06 sec   191 MBytes   159 Mbits/sec  54.183/ 8.026/150.243/16.781 ms (1526/131072) 1.03 MByte 366.98  7636=2948:2449:1258:498:175:185:75:48
 .TP
-.B where (per -e,)
+.B where (per \-e,)
 .B Burst Latency
 One way TCP write() to read() latency in mean/minimum/maximum/standard deviation format
 (Note: requires the client's and server's system clocks to be
@@ -407,7 +404,7 @@ Average burst size in bytes (computed av
 .br
 .B inP
 inP, short for in progress, is the average number of bytes in progress or in flight. This is taken from the application level write to read perspective. Note this is
-a mean value. The parenthesis value is the standard deviation from the mean.  (Requires --trip-times on client. See Little's law in NOTES.)
+a mean value. The parenthesis value is the standard deviation from the mean.  (Requires \-\-trip\-times on client. See Little's law in NOTES.)
 .br
 .B NetPwr
 Network power defined as (throughput / one way latency)
@@ -416,9 +413,9 @@ Network power defined as (throughput / o
 
 .B UDP tests (client)
 
-.B iperf -c <host> -e -i 1 -u -b 10m
+.B iperf \-c <host> \-e \-i 1 \-u \-b 10m
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 Client connecting to <host>, UDP port 5001 with pid 5169
 .br
@@ -426,7 +423,7 @@ Sending 1470 byte datagrams, IPG target:
 .br
 UDP buffer size:  208 KByte (default)
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 [  3] local 45.56.85.133 port 32943 connected with 45.33.58.123 port 5001
 .br
@@ -459,7 +456,7 @@ UDP buffer size:  208 KByte (default)
 [  3] 0.00-10.00 sec  11.9 MBytes  10.0 Mbits/sec   0.047 ms    0/ 8504 (0%)  0.537/ 0.392/23.657/ 0.497 ms  850 pps  2329.37
 .br
 .TP
-.B where (per -e,)
+.B where (per \-e,)
 .B Write/Err
 Total number of successful socket writes. Total number of non-fatal socket write errors
 .br
@@ -469,9 +466,9 @@ Transmit packet rate in packets per seco
 .PP
 
 .B UDP tests (server)
-.B iperf -s -i 1 -w 4M -u
+.B iperf \-s \-i 1 \-w 4M \-u
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 Server listening on UDP port 5001
 .br
@@ -479,7 +476,7 @@ Receiving 1470 byte datagrams
 .br
 UDP buffer size: 8.00 MByte (WARNING: requested 4.00 MByte)
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 [  3] local 192.168.1.4 port 5001 connected with 192.168.1.1 port 60027 (WARN: winsize=8.00 MByte req=4.00 MByte) (trip-times) (0.0) (peer 2.0.14-alpha)
 .br
@@ -511,7 +508,7 @@ UDP buffer size: 8.00 MByte (WARNING: re
 .br
 
 .TP
-.B where (per -e,)
+.B where (per \-e,)
 .B Latency
 End to end latency in mean/minimum/maximum/standard deviation format
 (Note: requires the client's and server's system clocks to be
@@ -522,7 +519,7 @@ PTP. A GPS disciplined OCXO is a recomme
 Received packet rate in packets per second
 .br
 .B inP
-inP, short for in progress, is the average number of bytes in progress or in flight. This is taken from an application write to read perspective. (Requires --trip-times on client. See Little's law in NOTES.)
+inP, short for in progress, is the average number of bytes in progress or in flight. This is taken from an application write to read perspective. (Requires \-\-trip\-times on client. See Little's law in NOTES.)
 .br
 .B NetPwr
 Network power defined as (throughput / latency)
@@ -531,9 +528,9 @@ Network power defined as (throughput / l
 
 .B Isochronous UDP tests (client)
 
-.B iperf -c 192.168.100.33 -u -e -i 1 --isochronous=60:100m,10m --realtime
+.B iperf \-c 192.168.100.33 \-u \-e \-i 1 \-\-isochronous=60:100m,10m \-\-realtime
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 Client connecting to 192.168.100.33, UDP port 5001 with pid 14971
 .br
@@ -541,7 +538,7 @@ UDP isochronous: 60 frames/sec mean= 100
 .br
 UDP buffer size:  208 KByte (default)
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 [  3] local 192.168.100.76 port 42928 connected with 192.168.100.33 port 5001
 .br
@@ -576,7 +573,7 @@ UDP buffer size:  208 KByte (default)
 [  3] 0.00-9.98 sec   120 MBytes   101 Mbits/sec   0.009 ms  196/85867 (0.23%)  0.665/ 0.083/ 1.318/ 0.174 ms 8605 pps  18903.85
 .br
 .TP
-.B where (per -e,)
+.B where (per \-e,)
 .B frames:tx/missed/slips
 Total number of isochronous frames or bursts. Total number of frame ids not sent. Total number of frame slips
 
@@ -584,9 +581,9 @@ Total number of isochronous frames or bu
 
 .B Isochronous UDP tests (server)
 
-.B iperf -s -e -u --udp-histogram=100u,2000 --realtime
+.B iperf \-s \-e \-u \-\-udp\-histogram=100u,2000 \-\-realtime
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 Server listening on UDP port 5001 with pid 5175
 .br
@@ -594,7 +591,7 @@ Receiving 1470 byte datagrams
 .br
 UDP buffer size:  208 KByte (default)
 .br
-------------------------------------------------------------
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 .br
 [  3] local 192.168.100.33 port 5001 connected with 192.168.100.76 port 42928 isoch (peer 2.0.13-alpha)
 .br
@@ -602,9 +599,9 @@ UDP buffer size:  208 KByte (default)
 .br
 [  3] 0.00-9.98 sec   120 MBytes   101 Mbits/sec   0.010 ms  196/85867 (0.23%)  0.665/ 0.083/ 1.318/ 0.284 ms 8585 pps  18903.85  601/1
 .br
-[  3] 0.00-9.98 sec T8(f)-PDF: bin(w=100us):cnt(85671)=1:2,2:844,3:10034,4:8493,5:8967,6:8733,7:8823,8:9023,9:8901,10:8816,11:7730,12:4563,13:741,14:1 (5.00/95.00%=3/12,Outliers=0,obl/obu=0/0)
+[  3] 0.00-9.98 sec T8(f)-PDF: bin(w=100us):cnt(85671)=1:2,2:844,3:\:10034,4:8493,5:8967,6:8733,7:8823,8:9023,9:8901,10:8816,11:7730,12:\:4563,13:741,14:1 (5.00/95.00%=3/12,Outliers=0,obl/obu=0/0)
 .br
-[  3] 0.00-9.98 sec F8(f)-PDF: bin(w=100us):cnt(598)=15:2,16:1,17:27,18:68,19:125,20:136,21:103,22:83,23:22,24:23,25:5,26:3 (5.00/95.00%=17/24,Outliers=0,obl/obu=0/0)
+[  3] 0.00-9.98 sec F8(f)-PDF: bin(w=100us):cnt(598)= 15:2,16:1,17:\:27,18:68,19:125,20:136,21:103,22:83,23:22,24:23,25:5,26:3 (5.00/95.00%=17/24,Outliers=0,obl/obu=0/0)
 
 .TP
 .B where,
@@ -634,68 +631,68 @@ Lowercase format characters are 10^3 bas
 based, e.g. 1k = 1000, 1K = 1024, 1m = 1,000,000 and 1M = 1,048,576
 .P
 .B Rate limiting:
-The -b option supports read and write rate limiting at the application level.  The -b option
+The \-b option supports read and write rate limiting at the application level.  The \-b option
 on the client also supports variable offered loads through the <mean>,<standard deviation> format, e.g.
 -b 100m,10m. The distribution used is log normal. Similar for the isochronous
-option. The -b on the server rate limits the reads. Socket based pacing is also
-supported using the --fq-rate long option. This will work with the --reverse
-and --full-duplex options as well.
+option. The \-b on the server rate limits the reads. Socket based pacing is also
+supported using the \-\-fq\-rate long option. This will work with the \-\-reverse
+and \-\-full\-duplex options as well.
 .P
 .B Synchronized clocks:
-The --trip-times option indicates that the client's and server's clocks are synchronized to a common reference.
+The \-\-trip\-times option indicates that the client's and server's clocks are synchronized to a common reference.
 Network Time Protocol (NTP) or Precision Time Protocol (PTP) are commonly used for
 this. The reference clock(s) error and the synchronization protocols will affect
 the accuracy of any end to end latency measurements.
 .P
 .B
 Binding
-is done at the logical level (ip address or layer 3) using the -B option
+is done at the logical level (ip address or layer 3) using the \-B option
 and at the device (or layer 2) level using the percent (%) separator for both the client
-and the server. On the client, the -B option affects the \fBbind\fR(2)
-system call, and will set the source ip address and the source port, e.g. iperf -c <host>
+and the server. On the client, the \-B option affects the \fBbind\fR(2)
+system call, and will set the source ip address and the source port, e.g. iperf \-c <host>
 -B 192.168.100.2:6002. This controls the packet's source values but not routing.
 These can be confusing in that a route or device lookup may not
 be that of the device with the configured source IP.
-So, for example, if the IP address of eth0 is used for -B and the
+So, for example, if the IP address of eth0 is used for \-B and the
 routing table for the destination IP address resolves
 the output interface to be eth1, then the host will send the packet
 out device eth1 while using the source IP address of eth0 in the packet.
 To affect the physical output interface (e.g. dual homed systems) either use
 -c <host>%<dev> (requires root) which bypasses this host route table lookup,
-or configure policy routing per each -B source address and set the
+or configure policy routing per each \-B source address and set the
 output interface appropriately in the policy routes. On the server or receive,
-only packets destined to -B IP address will be received. It's also useful
-for multicast. For example, iperf -s -B 224.0.0.1\fB%eth0\fR
+only packets destined to \-B IP address will be received. It's also useful
+for multicast. For example, iperf \-s \-B 224.0.0.1\fB%eth0\fR
 will only accept ip multicast packets with dest ip 224.0.0.1 that are
-received on the eth0 interface, while iperf -s -B 224.0.0.1 will
+received on the eth0 interface, while iperf \-s \-B 224.0.0.1 will
 receive those packets on any interface,
 Finally, the device specifier is required for v6 link-local,
-e.g. -c [v6addr]%<dev> -V, to select the output interface.
+e.g. \-c [v6addr]%<dev> \-V, to select the output interface.
 .P
 .B Reverse, full-duplex, dualtest (-d) and tradeoff (-r):
-The \fB--reverse\fR (-R) and \fB--full-duplex\fR options can be confusing when compared to the
-older options of \fB--dualtest (-d)\fR and \fB--tradeoff (-r)\fR. The newer options of \fB--reverse\fR and \fB--full-duplex\fR only
-open one socket and read and write to the \fBsame socket descriptor\fR, i.e. use the socket in full duplex mode.  The older -d and -r open
+The \fB\-\-reverse\fR (-R) and \fB\-\-full\-duplex\fR options can be confusing when compared to the
+older options of \fB\-\-dualtest (-d)\fR and \fB\-\-tradeoff (-r)\fR. The newer options of \fB\-\-reverse\fR and \fB\-\-full\-duplex\fR only
+open one socket and read and write to the \fBsame socket descriptor\fR, i.e. use the socket in full duplex mode.  The older \-d and \-r open
 second sockets in the opposite direction and do not use a socket in full duplex mode. Note that full duplex applies to the socket
 and not to the network devices and that full duplex sockets are supported by the
 operating systems regardless if an underlying network supports full duplex transmission and reception.
-It's \fBsuggested to use --reverse\fR if you
-want to \fBtest through a NAT firewall\fR (or -R on non-windows systems). This applies
-role reversal of the test after opening the full duplex socket.  (Note: Firewall piercing may be required to use -d and -r
+It's \fBsuggested to use \-\-reverse\fR if you
+want to \fBtest through a NAT firewall\fR (or \-R on non-windows systems). This applies
+role reversal of the test after opening the full duplex socket.  (Note: Firewall piercing may be required to use \-d and \-r
 if a NAT gateway is in the path.)
 .P
-Also, the --reverse -b <rate> setting behaves differently for TCP and UDP. For
+Also, the \-\-reverse \-b <rate> setting behaves differently for TCP and UDP. For
 TCP it will rate limit the read side, i.e. the iperf client
 (role reversed to act as a server) reading from the full duplex socket.
 This will in turn flow control the reverse traffic per standard TCP
-congestion control. The --reverse -b <rate> will be applied on
+congestion control. The \-\-reverse \-b <rate> will be applied on
 transmit (i.e. the server role reversed to act as a client) for UDP
 since there is no flow control with UDP. There is no option to
-directly rate limit the writes with TCP testing when using --reverse.
+directly rate limit the writes with TCP testing when using \-\-reverse.
 .P
 .B TCP Connect times:
 The TCP connect time (or three way handshake) can be seen on the iperf
-client when the -e (--enhanced) option is set. Look for the
+client when the \-e (\-\-enhanced) option is set. Look for the
 ct=<value> in the connected message, e.g.in '[ 3] local 192.168.1.4
 port 48736 connected with 192.168.1.1 port 5001 \fB(ct=1.84 ms)\fR'
 shows the 3WHS took 1.84 milliseconds.
@@ -705,9 +702,9 @@ The packets per second calculation is do
 time. The time is taken from the previous last packet to the current last packet. It is not
 the sample interval time. The last packet can land at different times within an interval.
 This means that pps does not have to match rx bytes divided by the sample interval.
-Also, with --trip-times set, the packet time on receive is set by the sender's write
-time so pps indicates the end to end pps with --trip-times. The RX pps calculation is receive
-side only when -e is set and --trip-times is not set.
+Also, with \-\-trip\-times set, the packet time on receive is set by the sender's write
+time so pps indicates the end to end pps with \-\-trip\-times. The RX pps calculation is receive
+side only when -e is set and \-\-trip\-times is not set.
 .P
 \fBLittle's Law\fR in queuing theory is a theorem that determines the average number of items (L) in a stationary queuing system based on the average waiting time (W) of an item within a system and the average number of items arriving at the system per unit of time (lambda). Mathematically, it's L = lambda * W. As used here, the units are bytes. The arrival rate is taken from the writes.
 .P
@@ -719,20 +716,20 @@ For TCP receives, the delay is the write
 For UDP the delay is the end/end latency.
 Don't confuse this with the physics definition of power (delta
 energy/delta time) but more of a measure of a desirable property
-divided by an undesirable property. Also note, one must use -i
+divided by an undesirable property. Also note, one must use \-i
 interval with TCP to get this as that's what sets the RTT sampling
 rate. The metric is scaled to assist with human readability.
 .P
 .B Multicast:
-Iperf 2 supports multicast with a couple of caveats. First, multicast streams cannot take advantage of the -P option. The server will serialize multicast streams. Also, it's highly encouraged to use a -t on a server that will be used for multicast clients. That is because the single end of traffic packet sent from client to server may get lost and there are no redundant end of traffic packets.  Setting -t on the server will kill the server thread in the event this packet is indeed lost.
+Iperf 2 supports multicast with a couple of caveats. First, multicast streams cannot take advantage of the \-P option. The server will serialize multicast streams. Also, it's highly encouraged to use a \-t on a server that will be used for multicast clients. That is because the single end of traffic packet sent from client to server may get lost and there are no redundant end of traffic packets.  Setting \-t on the server will kill the server thread in the event this packet is indeed lost.
 .P
 .B Fast Sampling:
 Use
-.B ./configure --enable-fastsampling
+.B ./configure \-\-enable\-fastsampling
 and then compile from source to enable four digit (e.g. 1.0000) precision in reports' timestamps. Useful for sub-millisecond sampling.
 .SH DIAGNOSTICS
 Use
-.B ./configure --enable-thread-debug
+.B ./configure \-\-enable\-thread\-debug
 and then compile from source to enable both asserts and advanced debugging of the tool itself.
 .SH BUGS
 See https://sourceforge.net/p/iperf2/tickets/
