Skip to content

Suggestion: include iperf3 for network speed testing #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
WiteWulf opened this issue Mar 18, 2021 · 3 comments
Open

Suggestion: include iperf3 for network speed testing #10

WiteWulf opened this issue Mar 18, 2021 · 3 comments

Comments

@WiteWulf
Copy link

WiteWulf commented Mar 18, 2021

Addition of the iperf3 binary to the linux sub system will allow detailed speed testing of network infrastructure, and wired and wireless adapters. This is particularly useful for users with USB wifi adapters whose drivers often misreport the PHY rate and provide sub-optimal connections.

NB. iperf3 does not utilise storage, so speed tests are not constrained by storage subsystems on the client or server.

https://github.com/esnet/iperf

@sorgelig
Copy link
Member

sorgelig commented Mar 19, 2021

MiSTer is mainly offline device, so i don't see a point to include it into distro. Presence of network on MiSTer is simply enough.
But you can compile binary and place it into /media/fat/linux/
It will be independent from linux releases.

@WiteWulf
Copy link
Author

I appreciate that that may be your personal use case, and that is what takes priority as the senior developer, but many people use network storage for the MiSTer and this would be very helpful for trouble-shooting. Having a network connection that is operating poorly can be worse than not having one at all. I'm a network engineer rather than a developer (hence my request for a network testing tool) and cross compiling binaries for ARM turned out to be beyond my skills after trying.

Thanks for taking the time to consider and respond, though. Feel free to close the issue.

@sorgelig
Copy link
Member

I'm not talking about my personal use case. I'm talking how MiSTer is designed. You may use network storage but any issues related to remote storage won't be accepted. Some cores aren't tolerating long delays when they access the storage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants