Speed Testing #13
Replies: 2 comments 5 replies
-
That's a great idea. This is officially on my to-do list now. I'll have to read up on the Apache 2.0 license to make sure it will play nice with my GPL-3 but since it's already written in Python, it should be fairly easy to integrate. I'm currently finishing up a web interface overhaul of my other project 'Kootnet Sensors', but once I'm done that, I'll see about this. |
Beta Was this translation helpful? Give feedback.
-
I have uploaded a development build with the option to use SpeedTest.net (speedtest-cli). It's all built-in, so you should be able to just upgrade and run it (Make sure to do the Dev upgrade). I don't have it set up to show previous results yet, but you can run it and see the results of that test on the web interface and with the hardware E-Ink screen. Let me know how it goes. I'll add in other stuff like options and things later. Right now it's all automatic. |
Beta Was this translation helpful? Give feedback.
-
Hey! Thanks for replying at RPi forums.
So my small suggestion is for option 3 that currently does nothing. I was thinking that it could be used to test the speed from the ISP. Separate from iperf testing, you'd know what your ISP was pushing you without having to get on your phone or PC and doing a speed test. So for me, when working in a tight networking closet, it would be super helpful to be able to do this without getting out and doing tests elsewhere 😛 .
What I was thinking is that, option 3 would temporarily turn on dhcp, pull an IP from the router, and run a speed test against the ethernet, output the results, then disable dhcp again.
One tool is speedtest-cli, which can be used to specify the IP address of the ethernet adapter to bind to:
speedtest-cli --source 10.1.1.3
for example.We can parse out info with either --simple or --json options:
What do you think?
Edit: Grammar
Beta Was this translation helpful? Give feedback.
All reactions