Please consider adding iperf3 to grml-small

[Zugschlus]

Hi,

it would be very useful to have iperf3 included in grml-small.

Greetings
Marc

[mika]

Hm, we already ship iperfwith grml-full, quoting from https://sourceforge.net/projects/iperf2/

Iperf 2 vs iperf 3 major differences: Iperf 2 here has timing related stats including end/end packet latency w/histograms (clocks assumed to be synced); supports multicast including SSM; supports threaded operation; supports L2 length checks. Iperf3 is a "cleaner" code base per a rewrite; supports json output; uses a test connection; is single threaded.

@Zugschlus is that still valid from your PoV, or to phrase it different: is there any reason why we should include iperf and iperf3 on grml-full (grml-small should be a subset of grml-full and if something is shipped on grml-small it should usually also be part of grml-full)? Is that a common situation, that users might need iperf3 without having the option to just install it on demand on the live system?

@grml/team-grml-developers opinions WRT iperf3 in grml-small? It's adding only ~328kb of disk space.

[Zugschlus]

I have always used iperf3, thinking that iperf3 was the successor to iperf2. I didn't know that iperf2 has features that iperf3 doesn't have. Reinstalling on demand might not always be an option since you might not have Internet at the place where you do your tests. I'd love to have both tools available.

[mika]

The daily ISOs as of tomorrow will include iperf3 in grml-small + grml-full. Thanks for your suggestion, @Zugschlus