ntttcp only has packages for Debian, Ubuntu, and NetBSD: https://pkgs.org/download/nttcp https://pkgs.org/download/nttcp No user of the other commercial Linux

ntttcp only has packages for Debian, Ubuntu, and NetBSD: https://pkgs.org/download/nttcp https://pkgs.org/download/nttcp No user of the other commercial Linux distros (RHEL, SLES) is going to install ntttcp from source or random binaries. Of course, the Windows kernel team could support POSIX system calls that iperf and other network applications require, instead of removing that feature altogether: https://learn.microsoft.com/en-us/archive/technet-wiki/10224.posix-and-unix-support-in-windows https://learn.microsoft.com/en-us/archive/technet-wiki/10224... But hey why provide customers a good product when you can just write a blog with a useless recommendation instead. Microsoft is a big company with many teams on many products. Some of those teams really understand interoperability with modern developers and applications. This team don't.