From 9e3c08824c9b6ea991b59a4d7745fd9fee5caaf4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Nikola=20Forr=C3=B3?= <nforro@redhat.com>
Date: Thu, 8 Aug 2019 17:37:57 +0200
Subject: [PATCH 5/6] iperf3.1: remove unsupported options
---
 iperf3/man1/iperf3.1 | 21 ---------------------
 1 file changed, 21 deletions(-)

diff --git a/iperf3/man1/iperf3.1 b/iperf3/man1/iperf3.1
index 0f42d5d..3cb3fc8 100644
--- a/iperf3/man1/iperf3.1
+++ b/iperf3/man1/iperf3.1
@@ -91,9 +91,6 @@ handle one client connection, then exit.
 .BR -c ", " --client " \fIhost\fR"
 run in client mode, connecting to the specified server
 .TP
-.BR --sctp
-use SCTP rather than TCP (FreeBSD and Linux)
-.TP
 .BR -u ", " --udp
 use UDP rather than TCP
 .TP
@@ -173,24 +170,6 @@ set the IP 'type of service'
 .BR -L ", " --flowlabel " \fIn\fR"
 set the IPv6 flow label (currently only supported on Linux)
 .TP
-.BR -X ", " --xbind " \fIname\fR"
-Bind SCTP associations to a specific subset of links using sctp_bindx(3).
-The \fB--B\fR flag will be ignored if this flag is specified.
-Normally SCTP will include the protocol addresses of all active links
-on the local host when setting up an association. Specifying at least
-one \fB--X\fR name will disable this behaviour.
-This flag must be specified for each link to be included in the
-association, and is supported for both iperf servers and clients
-(the latter are supported by passing the first \fB--X\fR argument to bind(2)).
-Hostnames are accepted as arguments and are resolved using
-getaddrinfo(3).
-If the \fB--4\fR or \fB--6\fR flags are specified, names
-which do not resolve to addresses within the
-specified protocol family will be ignored.
-.TP
-.BR --nstreams " \fIn\fR"
-Set number of SCTP streams.
-.TP
 .BR -Z ", " --zerocopy " "
 Use a "zero copy" method of sending data, such as sendfile(2),
 instead of the usual write(2).
-- 
2.21.0