Testing on a 5GBs fiber link:
Of the four options built into the route10 for testing the speed of a link the max reported speed hovers around 1gbs u/d
Testing on a computer to the local speedtest.net site shows me ~2.4GBs u/d (my pc currently only has a 2.5 nic as I am not looking to saturate the link with any one device day-to-day) so I know the connection is faster than what the built in test is reporting.
I would like to be able to accurately test my fiber backbone. Can we possibly get some test locations that can actually reach 10gbs? Or is it a bug in the built-in test?
Yeah, we have resorted to using ookla speedtest on the route10 via CLI as it is much more accurate. In our area the built in speed test limits at about 400-500mbps whereas I can get 9.4Gbps on the ookla speedtest via cli on route10.
As i said in the OP:
Testing on a computer to the local speedtest.net site shows me ~2.4GBs u/d (my pc currently only has a 2.5 nic as I am not looking to saturate the link with any one device day-to-day) so I know the connection is faster than what the built in test is reporting.
Perfect, If you create a /cfg/post-cfg.sh file in the cli on the route10 and paste the following in (fyi, this isn’t my code, I believe it was @dalewhlrr)
to create the post-cfg file:
nano /cfg/post-cfg.sh
The contents of post-cfg.sh should be (you might already have this done and/or other stuff in here, but this is the speedtest specific portion:
#!/bin/sh
# === Persistent Installation Path ===
SPEEDTEST_BIN="/usr/bin/speedtest"
SPEEDTEST_DIR="/cfg/speedtest"
SPEEDTEST_URL="https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux->
# === Check if speedtest is already installed ===
if [ ! -f "$SPEEDTEST_BIN" ]; then
echo "Speedtest not found, downloading..."
mkdir -p "$SPEEDTEST_DIR"
cd "$SPEEDTEST_DIR"
wget -q "$SPEEDTEST_URL"
tar -xvzf ookla-speedtest-*.tgz
if [ -f "$SPEEDTEST_DIR/speedtest" ]; then
mv "$SPEEDTEST_DIR/speedtest" "$SPEEDTEST_BIN"
chmod +x "$SPEEDTEST_BIN"
echo "Speedtest installed successfully."
else
echo "Error: Speedtest binary not found after extraction!"
fi
else
echo "Speedtest already installed."
fi
Once you do that, save and exit (ctrl+x) and run the command to make the file executable:
chmod +x /cfg/post-cfg.sh
Then you can run it once if you’d like:
/cfg/post-cfg.sh
That will install ookla speedtest. It will also keep it on Route10 reboot. To use ookla speedtest using the closest server just type the following in the CLI:
speedtest
Some other fun things that might help is to list all the servers:
speedtest --L
and then the following to run to a certain server, replace “server-id” with the id of the server in the previous command:
speedtest -s "server-id"
Also, for help at any time, you can use the following:
speedtest --help
Hope this works well for you. Good luck and let me know if you need anything!
I would always test your WAN speed using iperf3 instead of a browser-based speed test. You can find lists of public iperf3 servers online, along with their maximum bandwidth and the exact command to run.
In my experience, it’s far more reliable than running Speedtest.net in a web browser. I’ve seen browser-based tests cap out at 400–500 Mbps, while iperf3 consistently showed 960 Mbps on the same connection.
This is useful feedback, thanks! For some insight into our current implementation: it uses Measurement Labs, which is an open consortium for testing internet performance. We’re interested in supporting their growth and mission, which are admittedly not the same as Ookla’s, e.g. MLab intentionally tries to dispatch to a server in a different ISP to provide a more real world throughput measure. Unfortunately, we have seen regions with less performant speed test servers with MLab infrastructure.
Yes I’m sure they would! Actually anyone can host a server and we’re willing to help anyone get started. Check out their hosting documentation and email if you have any questions. I can get you connected with some MLabs folks.
I now have an M-Lab server up and running and my Route10 recognizes it and can run tests to it at over 7G. Thank you for helping with this. I can now trust the M-Lab tests in Route10.