4 ms·
Perhaps Microsoft should work with OpenWRT to get the linux version of ntttcp incorporated and built for routers as a package. I use iperf2/iperf3 because it is
by molticrystal 2y ago
Perhaps Microsoft should work with OpenWRT to get the linux version of ntttcp incorporated and built for routers as a package. I use iperf2/iperf3 because it is provided by opkg.
- luma 2y agoI think this is the key problem with their recommendation - it presumes that I'm running Windows on both sides of the test. iperf is neat because it runs on just about anything which allows you to run a binary which is really handy in datacenter troubleshooting situations.
- pseudosavant 2y agoMy first thought was "I bet getting ntttcp on x86 with Ubuntu/CentOS is ok, but I doubt it will be simple for something like OpenWRT." root@router:~# opkg find ntttcp root@router:~# opkg install ntttcp Unknown package 'ntttcp'. Collected errors: * opkg_install_cmd: Cannot install package ntttcp. root@router:~# Microsoft would be so much better served putting resources into proper Windows support for iperf3, instead of creating their own tools and convincing the world to switch.
- rixthefox 2y agoI would suspect Microsoft's corporate culture is to blame for that. If you make a tool that "already works on Windows" work you don't get any extra praise. If you however come up with a brand new thing you'll get a slap on the back and a raise!
- suprjami 2y agoThere are only packages for Debian, Ubuntu, and NetBSD. Not even include-everything Arch or Gentoo has ntttcp apparently.