iperf installed - ...but not really installed?

English Install/Boot/Login
1

Hello!

I did this on two installs of 15.1 with identical results, what am I missing here?

abcdefg@host:~> sudo zypper in iperf
[sudo] password for root: 
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 2 NEW packages are going to be installed:
  iperf libiperf0

2 new packages to install.
Overall download size: 111.2 KiB. Already cached: 0 B. After the operation, additional 218.7 KiB will be used.
Continue? [y/n/v/...? shows all options] (y): y
Retrieving package libiperf0-3.5-lp151.2.3.x86_64                                                     (1/2),  72.1 KiB (160.8 KiB unpacked)
Retrieving: libiperf0-3.5-lp151.2.3.x86_64.rpm ......................................................................................[done]
Retrieving package iperf-3.5-lp151.2.3.x86_64                                                         (2/2),  39.1 KiB ( 57.9 KiB unpacked)
Retrieving: iperf-3.5-lp151.2.3.x86_64.rpm ..........................................................................................[done]
Checking for file conflicts: ........................................................................................................[done]
(1/2) Installing: libiperf0-3.5-lp151.2.3.x86_64 ....................................................................................[done]
(2/2) Installing: iperf-3.5-lp151.2.3.x86_64 ........................................................................................[done]
abcdefg@host:~> iperf -s
If 'iperf' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf iperf
abcdefg@host:~> cnf iperf
 iperf: command not found
2

OMG, it’s on openSUSE

iperf3 -s

…

3

Yes, a new version, and not compatible with older version.

4

For the future:

You install a package by the package name. This is not necessary the name of any executable file that is installed with the package. There may be nil, one, or more executables in a package, but none of the names of those files is by necessaty the name of the package.

Also, even if there is an executable file installed with the package, it may not be installed in a directory that is included in the PATH variable as used by the majority of users.

Thus, after a package installed, you can e.g. search and select the package in YaST > Software > Software Management and then choose the File list tab lower right. A list of files installed with the packet shows and to make it easy for humean interpretation, the executables are in bold there.