Speedtest on Flint

Im looking to speedtest directly from the flint router. I am using it as a wireguard server and need to make sure that my speed loss is from vpn service vs actual service as i have it setup in an area that i dont frequent often.

I can do a little comman line but honestly not good at doing what i dont know. I have windows and can follow directions but sometimes have to be very blunt with telling me what to do.

I know there are ways to install the speedtest to operate in cli. I have another modem/router than has it built in and can operate it just fine. I just dont know how. Any help would be much appreciated

1 Like

This should work:

1 Like

You could search here in this forum, where this topic is solved more than once: Search results for 'Speedtest' - GL.iNet

And if there are specific questions unanswered, feel free to ask.

2 Likes

from the most relevant that I could find this is what I get

root@GL-AX1800:~# wget https://install.speedtest.net/app/cli/ookla-speedtest-1.2
.0-linux-aarch64.tgz && tar xzf ookla
--2024-07-24 19:02:39-- https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-aarch64.tgz
Resolving install.speedtest.net... 151.101.42.219, 2a04:4e42:a::731
Connecting to install.speedtest.net|151.101.42.219|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1082287 (1.0M) [application/x-tar]
Saving to: 'ookla-speedtest-1.2.0-linux-aarch64.tgz.4'

ookla-speedtest-1.2 100%[===================>] 1.03M 689KB/s in 1.5s

2024-07-24 19:02:41 (689 KB/s) - 'ookla-speedtest-1.2.0-linux-aarch64.tgz.4' saved [1082287/1082287]

tar: can't open 'ookla': No such file or directory
root@GL-AX1800:~# -speedtest-1.2.0-linux-aarch64.tgz && ./speedtest
-ash: -speedtest-1.2.0-linux-aarch64.tgz: not found
root@GL-AX1800:~#

in the directory you download use :

tar xzvf ookla-speedtest-1.2.0-linux-aarch64.tgz.4 ; chmod +x speedtest ;./speedtest

I get that i have tried this multiple times so i get the .4 at the end of the file name. Just seems the last command that doesn't work

root@GL-AX1800:~# wget https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-aarch64.tgz
--2024-07-24 20:55:03-- https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-aarch64.tgz
Resolving install.speedtest.net... 146.75.94.219, 2a04:4e42:87::731
Connecting to install.speedtest.net|146.75.94.219|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1082287 (1.0M) [application/x-tar]
Saving to: 'ookla-speedtest-1.2.0-linux-aarch64.tgz.4'

ookla-speedtest-1.2. 100%[=====================>] 1.03M --.-KB/s in 0.06s

2024-07-24 20:55:03 (17.1 MB/s) - 'ookla-speedtest-1.2.0-linux-aarch64.tgz.4' saved [1082287/1082287]

root@GL-AX1800:~# tar xzvf ookla-speedtest-1.2.0-linux-aarch64.tgz.4
speedtest
speedtest.md
speedtest.5
root@GL-AX1800:~# chmod +x speedtest
root@GL-AX1800:~# ./speedtest
./speedtest: line 2: syntax error: unterminated quoted string
root@GL-AX1800:~#

Please delete all speedtest files and try the command again. Make sure that you visit the original and linked thread before you copy the command.

As @admon said use : rm speed* to delete all the files because you have many duplicates

same results as before with the last command ./speedtest not working

The original post with commands does not work because of the line break. So if you just straight copy it will fail. These are the commands that I have entered with the results

rm ookla*

wget https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-aarch64.tgz

tar xzvf ookla-speedtest-1.2.0-linux-aarch64.tgz

chmod +x speedtest

./speedtest

root@GL-AX1800:~#
root@GL-AX1800:~# rm ookla*
root@GL-AX1800:~#
root@GL-AX1800:~# wget https://install.speedtest.net/app/cli/ookla-speedtest-1.2
.0-linux-aarch64.tgz
--2024-07-25 13:26:47-- https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-aarch64.tgz
Resolving install.speedtest.net... 146.75.94.219, 2a04:4e42:87::731
Connecting to install.speedtest.net|146.75.94.219|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1082287 (1.0M) [application/x-tar]
Saving to: 'ookla-speedtest-1.2.0-linux-aarch64.tgz'

ookla-speedtest-1.2 100%[===================>] 1.03M --.-KB/s in 0.06s

2024-07-25 13:26:48 (17.0 MB/s) - 'ookla-speedtest-1.2.0-linux-aarch64.tgz' saved [1082287/1082287]

root@GL-AX1800:~#
root@GL-AX1800:~# tar xzvf ookla-speedtest-1.2.0-linux-aarch64.tgz
speedtest
speedtest.md
speedtest.5
root@GL-AX1800:~#
root@GL-AX1800:~# chmod +x speedtest
root@GL-AX1800:~#
root@GL-AX1800:~# ./speedtest
./speedtest: line 2: syntax error: unterminated quoted string
root@GL-AX1800:~#
root@GL-AX1800:~#

I think the main issue here is the understanding.

./speedtest seems to be a shell script.
A shell script could be written for different shells. bash, dash, ash, zsh, csh, ... but mostly it is compatible with bash.

Since it seems no one here has ssh access to a router, capable of ssh to get and execute the script, it could maybe important to know what is written in line 2 of the script 'speedtest'.

If I remember correct, there are more than one solutions written in my link. Just in case the ookla Skript is broken for this architecture/shell at this moment.
Else you make a big report against Ookla or you wait until someone do it for you. But to file a bug report, you should understand the script and the implications.

Since I don't want to rally on 3rd party endpoints, my setup is two iperf3 installations at endpoints, manages by me. So the ookla solution is a workaround in unmanaged environments. In that case the use of a capable endpoint with browser (laptop/mobile) works fine for me.

It is all a question what you want to archive and how much you want to invest to get this goal... Here is no ookla support. If this one solution does not work, you should search for an alternative? Even if debugging should be easy.

For AX1800 Flint and AXT1800 Slate AX, you need to use this one

https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-armel.tgz

From Speedtest CLI: Internet speed test for the command line
image

2 Likes

Argh. Long time no Flint usage for me, I thought it was aarch64 as well.

My fault, sorry!

I have to test and confirm as well.

Okay, wrong architecture ... Haven't thought on this one. I focused on the quoted line. Sounds like a shell script.

Note: ask for echo $ARCH on devices I don't own. Or lsb_release -a? What is the best command for (almost) all GL.iNet devices?

uname -a works fine.

But there is a special case: GL.iNet GL-MT1300
It will return mips, but it is mipsel.

3 Likes

Thank you for the help as this has worked. I have never seen where it outputs all the updates of the speedtest during the test. I have another flint that I ran this on and it does the simplified output. The other router I have also outputs the simplified output. I am not worried about it but just odd that two of the same router do different outputs. I understand that its an ookla script so I am not going to investigate, just wanted to know if anybody has run into this before.
Again thanks for all your help

rm ookla*

wget https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-armel.tgz

tar xzvf ookla-speedtest-1.2.0-linux-armel.tgz

./speedtest

root@GL-AX1800:~# ./speedtest

Speedtest by Ookla

[error] Error: [101] Network unreachable
[error] Error: [101] Network unreachable
Server: Sonic.net, Inc. - Santa Rosa, CA (id: 62981)
ISP: T-Mobile USA
Idle Latency: 53.96 ms (jitter: 27.29ms, low: 34.95ms, high: 73.79ms)
Download: 9.08 Mbps [| ] 4% - latency: 191.78 ms Download: 8.64 Mbps [/ ] 4% - latency: 191.78 ms Download: 8.29 Mbps [=- ] 5% - latency: 191.78 ms Download: 8.03 Mbps [=\ ] 6% - latency: 191.78 ms Download: 7.80 Mbps [=| ] 6% - latency: 191.78 ms Download: 7.93 Mbps [=/ ] 7% - latency: 191.78 ms Download: 8.02 Mbps [=- ] 8% - latency: 295.39 ms Download: 8.62 Mbps [=\ ] 8% - latency: 295.39 ms Download: 8.91 Mbps [=| ] 9% - latency: 295.39 ms Download: 9.10 Mbps [==/ ] 10% - latency: 295.39 ms Download: 9.64 Mbps [==- ] 10% - latency: 295.39 ms Download: 10.21 Mbps [==\ ] 11% - latency: 295.39 ms Download: 10.31 Mbps [==| ] 12% - latency: 178.68 ms Download: 10.87 Mbps [==/ ] 12% - latency: 178.68 ms Download: 11.19 Mbps [==- ] 13% - latency: 178.68 ms Download: 11.68 Mbps [==\ ] 14% - latency: 178.68 ms Download: 12.02 Mbps [==| ] 14% - latency: 178.68 ms Download: 12.27 Mbps [===/ ] 15% - latency: 178.68 ms Download: 14.29 Mbps [===- ] 16% - latency: 178.68 ms Download: 14.38 Mbps [===\ ] 16% - latency: 130.62 ms Download: 14.37 Mbps [===| ] 17% - latency: 130.62 ms Download: 14.78 Mbps [===/ ] 18% - latency: 130.62 ms Download: 14.89 Mbps [===- ] 18% - latency: 130.62 ms Download: 15.38 Mbps [===\ ] 19% - latency: 130.62 ms Download: 14.88 Mbps [====| ] 20% - latency: 130.62 ms Download: 14.41 Mbps [====/ ] 20% - latency: 130.62 ms Download: 13.89 Mbps [====- ] 21% - latency: 130.62 ms Download: 13.35 Mbps [====\ ] 22% - latency: 135.99 ms Download: 12.86 Mbps [====| ] 22% - latency: 135.99 ms Download: 12.35 Mbps [====/ ] 23% - latency: 135.99 ms Download: 12.17 Mbps [====- ] 24% - latency: 135.99 ms Download: 12.65 Mbps [====\ ] 24% - latency: 135.99 ms Download: 12.51 Mbps [=====| ] 25% - latency: 135.99 ms Download: 12.22 Mbps [=====/ ] 26% - latency: 135.99 ms Download: 11.99 Mbps [=====- ] 27% - latency: 135.99 ms Download: 11.67 Mbps [=====\ ] 27% - latency: 135.99 ms Download: 11.92 Mbps [=====| ] 28% - latency: 340.95 ms Download: 11.99 Mbps [=====/ ] 29% - latency: 340.95 ms Download: 11.89 Mbps [=====- ] 29% - latency: 340.95 ms Download: 11.84 Mbps [======\ ] 30% - latency: 340.95 ms Download: 11.93 Mbps [======| ] 31% - latency: 340.95 ms Download: 11.99 Mbps [======/ ] 31% - latency: 340.95 ms Download: 11.81 Mbps [======- ] 32% - latency: 181.64 ms Download: 11.73 Mbps [======\ ] 33% - latency: 181.64 ms Download: 11.60 Mbps [======| ] 33% - latency: 181.64 ms Download: 11.51 Mbps [======/ ] 34% - latency: 181.64 ms Download: 11.34 Mbps [=======- ] 35% - latency: 181.64 ms Download: 11.11 Mbps [=======\ ] 35% - latency: 181.64 ms Download: 11.02 Mbps [=======| ] 36% - latency: 262.68 ms Download: 11.06 Mbps [=======/ ] 37% - latency: 262.68 ms Download: 10.99 Mbps [=======- ] 37% - latency: 262.68 ms Download: 10.98 Mbps [=======\ ] 38% - latency: 262.68 ms Download: 10.83 Mbps [=======| ] 39% - latency: 262.68 ms Download: 10.76 Mbps [=======/ ] 39% - latency: 262.68 ms Download: 10.79 Mbps [========- ] 40% - latency: 246.39 ms Download: 10.80 Mbps [========\ ] 41% - latency: 246.39 ms Download: 10.73 Mbps [========| ] 41% - latency: 246.39 ms Download: 10.65 Mbps [========/ ] 42% - latency: 246.39 ms Download: 10.55 Mbps [========- ] 43% - latency: 246.39 ms Download: 10.69 Mbps [========\ ] 43% - latency: 213.68 ms Download: 10.77 Mbps [========| ] 44% - latency: 213.68 ms Download: 10.87 Mbps [=========/ ] 45% - latency: 213.68 ms Download: 10.86 Mbps [=========- ] 45% - latency: 213.68 ms Download: 10.86 Mbps [=========\ ] 46% - latency: 213.68 ms Download: 10.91 Mbps [=========| ] 47% - latency: 213.68 ms Download: 11.07 Mbps [=========/ ] 47% - latency: 140.01 ms Download: 11.23 Mbps [=========- ] 48% - latency: 140.01 ms Download: 11.24 Mbps [=========\ ] 49% - latency: 140.01 ms Download: 11.26 Mbps [=========| ] 49% - latency: 140.01 ms Download: 11.33 Mbps [==========/ ] 50% - latency: 140.01 ms Download: 11.34 Mbps [==========- ] 51% - latency: 127.64 ms Download: 11.24 Mbps [==========\ ] 51% - latency: 127.64 ms Download: 11.18 Mbps [==========| ] 52% - latency: 127.64 ms Download: 11.06 Mbps [==========/ ] 53% - latency: 127.64 ms Download: 11.02 Mbps [==========- ] 53% - latency: 127.64 ms Download: 11.14 Mbps [==========\ ] 54% - latency: 272.55 ms Download: 11.05 Mbps [===========| ] 55% - latency: 272.55 ms Download: 11.13 Mbps [===========/ ] 55% - latency: 272.55 ms Download: 11.20 Mbps [===========- ] 56% - latency: 272.55 ms Download: 11.20 Mbps [============\ ] 60% - latency: 190.68 ms Download: 11.20 Mbps [============| ] 64% - latency: 190.68 ms Download: 11.19 Mbps [=============/ ] 68% - latency: 190.68 ms Download: 11.20 Mbps [==============- ] 73% - latency: 190.68 ms Download: 11.20 Mbps [===============\ ] 77% - latency: 190.68 ms Download: 11.19 Mbps [================| ] 81% - latency: 190.68 ms Download: 11.19 Mbps [=================/ ] 86% - latency: 190.68 ms Download: 11.20 Mbps [==================- ] 90% - latency: 190.68 ms Download: 11.20 Mbps [==================\ ] 94% - latency: 190.68 ms Download: 11.19 Mbps [===================|] 99% - latency: 190.68 ms Download: 11.19 Mbps (data used: 11.7 MB)
190.68 ms (jitter: 57.64ms, low: 42.74ms, high: 600.36ms)

It seems your terminal emulator or your terminal is not build for interactive playback. So the output you see is ment to be provided in one line.

From the ookla documentation I can see the switch -p no to avoid the terminal flooding with wrong displayed progress bars:

-p yes|no –progress=yes|no
Enable or disable progress bar (default = yes when interactive)

Source: Speedtest CLI by Ookla · GitHub

Thats the funny thing. I connect to one flint and get that long output. Then connect to another flint and get the single line output. Im using putty with all the default settings as far as i know.

I will try out that option on the output