Quick and easy way to measure throughput between two nodes
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Quick and easy way to measure throughput between two nodes
I was in a situation earlier, where I was not allowed to install software on any servers, but I was expected to fix a networking problem that required me to test the throughput between two nodes on different networks.
Generally, at this point I would use 'iperf' but, being unable to install anything, I was unable to.
So I had to get around this somehow. Here is a simple solution for anyone caught in the same spot.
Hey, that looks pretty handy! I've never heard of pv up till now.
As I don't run fedora myself (and this isn't in the CentOS repositorys I'm used to frolicing in), I'm linking here;
This is "pipe viewer" (homepage here). Current version is 1.2.0, and it seems pretty flexible, too.
But be aware that on fast local networks (ie. anything Gigabit), your CPU may be the bottleneck in anything involving SSH. For example, my little Atom based CPU can only churn through data at about 20MB/s if SSH is involved.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.