Iperf version

stephenw10

I haven't seen anything about that.

iperf3 is available to install from the command line though if you need it:

pkg install iperf3
rehash

Steve

JKnott

@stephenw10

I hadn't realized you moved it and I created another thread in Packages > Traffic Monitoring. Still, pfSense should be upgraded to the current version.

JKnott

@stephenw10 said in Iperf version:

pkg install iperf3

I have installed it and it works, but doesn't appear under Diagnostics.

johnpoz

You do understand packages are not always "official" supported by pfsense developers right?

Looks like the last commits to that package were done by dok
https://github.com/pfsense/FreeBSD-ports/commits/devel/benchmarks/pfSense-pkg-iperf

Long time ago, and I doubt he will be back ever ;) Even though some of us miss his wise ass remarks and bluntness..

So if you want to take it over - sure it would be appreciated.. For something like iperf, that really doesn't have much use actually on pfsense anyway I doubt a gui for even makes much sense.. But sure go for it.

If anything there should prob be a listing, maybe there is and I have just not seen it of the packages you can use and install from the cmd line..

JKnott

@johnpoz said in Iperf version:

If anything there should prob be a listing, maybe there is and I have just not seen it of the packages you can use and install from the cmd line..

Yes, it works fine from the command line. However, given it's obsolete and not compatible with the current version, then maybe v2 should be deleted from the Package Manager.

stephenw10

I agree, it should be updated.

johnpoz

Yeah would concur either update the package to v3, or just remove it.

stephenw10

https://redmine.pfsense.org/issues/9765

stephenw10

And now available for testing in 2.5:

Installed packages to be UPGRADED:
	pfSense-pkg-iperf: 2.0.5.5_3 -> 3.0 [pfSense]

No additional options yet.

Steve

JKnott

I just installed v3 and it appears to work OK. However, in the graphical interface, it shows the default port as 5001, not 5201, which is the current default port. However, it does run with the correct 5201 port.

jimp

That was just a cosmetic issue and is corrected in the repo, so when the next build happens, it will be fixed.