Allow different control connection port number than data connection

[t-lin]

Context

UDP tests require a TCP control connection to be set up beforehand. This connection currently uses the same port number as the UDP port used for the test / data connection.

Consider an environment where the network between the client & server are comprised of one or more third-party network services (e.g. VPN, proxy, firewall, etc.) with very strict security policies. Only certain ports are opened, and no port number is opened for both TCP and UDP. It's very difficult to request a new port number be opened (when requesting a port, they return a randomized port number and only for one protocol).

I'd be willing to help if someone can point me to the files/functions to look at.

Enhancement Request

Allow users to specify the port number used for the control connection, different than the port number specified by -p which is used for the actual test data.

• Current behavior Control connection defaults to the same port number used for the test / data connection.

• Desired behavior Control connection uses a different port number than the test / data connection.

• Implementation notes Introduce a new flag to specify the control port? Ideally this flag should be applicable for both when iperf3 runs in server mode or client mode.

[deliciouslytyped]

We ran into a case where this would have been useful.

[davidBar-On]

Submitter PR #1790 that supports a UDP data streams port number that is different than the TCP control port number.