Speedtest By Ookla
Catrina Mayoka
I just reinstalled speedtest-cli on my router. It was about 10.5 MB. Make sure you have enough space before installing. You could probably delete most of the pip dependencies after installing speedtest. Ill try out which packages when I have some time. Now my speeds match my desktop but ping is definitely higher on the router, 4-5 ms on PC and 11-12 ms on OpenWRT.
The Python Speedtest is very different from the Ookla speedtest, and in my experience gives poor and erroneous results. I have a Raspberry Pi 4B I am using with OpenWRT. Before I installed OpenWRT on it, I ran up Raspian and installed the Python Speedtest. It only gave me around 80Mb/s even though my Virgin Media UK service was capable of 360Mb/s. I then downloaded the compiled Speedtest binary from Ookla and even when specifying the same server as the Python version, the results were much different - I got around 350-360Mb/s on every pass.
I understand the iPad has its own device limitations but the question originates why one app is reasonable speeds vs the other in speed measurement. It appears the ookla app is consistently slow across all tested platforms but the nighthawk app reflects speeds more inline with expected processing.
I understand the iPad has its own device limitations but the question originates why one app is reasonable speeds vs the other in speed measurement. It appears the ookla app is consistently slow across all tested platforms but the nighthawk app reflects speeds more inline with expected processing.
You can set up a file and web server (maybe even FTP) on a machine on your LAN and set up a Network binding speedtest Thing using that internal URL. The network binding can also be configured with a short ping time for online/offline tracking. But in general there are lots of way better tools for monitoring this sort of thing than openHAB.
What is strange is even if I have no wifi connection in my screen, the deco app internetspeedtest will give almost the same speeds....That is really strange...(zie image here under). Notice the absence of the wifi icon in the right upper corner and still the projects 478,1 down and 687,0 upload. Why is this?
If I use Ookla speedtest I have other speeds. 72Mbps download and 97,1 Mbps upload. THis is in the same room where I did the deco m5 speedtest in tp deco app. Why are the speeds so different? On the same device, same room, same spot? Can someone help me?
Still my wifi speed with ookla speedtest on the 1e floor with my mobilephone connected to my deco m5 on the 1e floor ap modus. I have checked it. Speed is 70 down and 90mbps up. Even next to the deco.
I was able to find a spot in my config that was using another default cert. now I can go to http(s)://speedtest.waveruralconnect.com:8080/5060 successfully. However, I am still getting a fail via https with the Ookla server tester.
That worked like a champ! I had a few minutes Bierce leaving for work to make the change in ooklaserver.properties file and restarted the ooklaserver daemon. I am now passing the ookla tester in all categories. Thanks again!
When i try to access ordinary web sites everything is OK! However, whenever i try to perform the well known speedtest (either from linux or windows hosts), the download speed increases quickly and then gradually drops. Eventually, all hosts in the network are temporarily denied acces to the internet for a few minutes (i have a ping -t running which proves that).
On the other hand, i tried other tests also and exactly the same occurs-but not in every case: I have the feeling this happens due my high-throughput broadband connection (1Gbps download / 1Gbps upload), because when i perform speedtests on other related sites that cannot sustain such high throughput, then there is no problem, ie no blocking appears!
Thanks for the response. My issue, I think, is the placement of the eero pods and doing an ookla speedtest showing low speeds (less than 100 mbps), even though the eero speedtest is showing very high speeds (400+ mbps) from the same location (like my bedroom). I've moved the pods around, but can't get many "sweet spots". Trial and error, I suppose. Also, eero seems to not show nearby devices consistently. Sometimes, a device is very near an eero pod, but the device shows up connected to a pod on the other side of the house (ranch-style).
My problem with this is that when I do a speed test from the app Im getting 980 ish... Mbps download and 200 ish... Mbps upload. Im not sure why its not showing the 500 Mbps upload speeds I should be getting. Alternatively Im showing the actual speeds are correct when doing a speedtest on ookla.
Here is the script to get data from ookla. Script is running speedtest cli version and generates xml output with four channels as one sensor. You will get Download, Upload, ping and distance to server.
In order to fix the problem of the speedtest command "The term" speedtest "is not recognized as the cmdlet name", I modified the result "$ result = C: \ speedtest \ speedtest.exe" and deleted the --csv --bytes options.For other errors, I commented out the following lines:
Ookla Speedtests are a way for users to find out the download speed, upload speed and latency of their internet connection. This is an analysis of the number of users who took the speedtest. To account for change, we take the baseline number of users from November 2022 to January 2023 and show the percent change in daily users and change in weekly users.
You can install it via brew or just download it directly from GitHub. If you install it via brew it will be at /opt/homebrew/bin/speedtest-cli on M1-based Macs or /usr/local/bin/speedtest-cli on Intel-based Macs.
You can use the original speedtest CLI utility from ookla. The one shipped with nethserver is an opensource one (there was some discussion about using or not using the one from ookla due to its license).
Some interloper wrote to this thread who was suspended for SPAM, but since they raised an issue claiming the CLI speedtest uses one server, and the portal uses more than one, I can report the following:
35fe9a5643