--username option usage #1455
-
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
If OpenSSL library library is available, you may try building iperf3 using |
Beta Was this translation helpful? Give feedback.
-
On the client side, the user name is set by the On the server side, the following two parameters must be set for the authorization to work:
|
Beta Was this translation helpful? Give feedback.
-
I assume the "a" file is the "credentials.csv" file in the Oracle example. Is this correct? (Note that they have a typo there: the "cat credentials.csv" should be "cat >credentials.csv".) Did you create the corresponding "public.pem" file and set the |
Beta Was this translation helpful? Give feedback.
-
Seems that you have not created and used the authorized users file correctly. You should first create the file. In the Oracle example the username is "mario" and the password is "rossi". Per that example, first create the password hash:
Then create the authorized users file "credentials.csv", where "bf7a49a846d44b454a5d11e7acfaf13d138bbe0b7483aa3e050879700572709b" is the password hash from the above:
Now, run the server using |
Beta Was this translation helpful? Give feedback.
On the client side, the user name is set by the
--username
and the password is set either by theIPERF3_PASSWORD
environment variable, or iperf3 will prompt for it. When using--username
,--rsa-public-key-path
must be set also.On the server side, the following two parameters must be set for the authorization to work:
--rsa-private-key-path
- the private key path.--authorized-users-path
- the path to the file that includes the user names and their password. This Oracle page has a good explanation about this file format and an example of generating it (see both the options descriptions and the EXAMPLES section).