Speedtest server

A subscriber who runs a speed test usually measures against a server somewhere else. With Ookla’s Speedtest server on the Super Router, the test runs against your own network, and it shows up in the Speedtest apps and on speedtest.net under your name.

The router downloads the server from Ookla, runs it, writes its settings and watches it. You never copy files or edit its configuration.

Install and start

dtvsol speedtest install        # downloads Ookla's server (run it again later: the latest)
dtvsol speedtest on
dtvsol speedtest                # running, version, its check, tests now, settings

It listens on ports 5060 and 8080 (TCP and UDP, IPv4 and IPv6), the ones speedtest.net uses. It runs as its own user, not as root, and uses at most 4 CPU cores by default (dtvsol speedtest set cpu 8): packet forwarding always keeps the rest.

A name and a certificate

The Speedtest web page talks to the server over HTTPS, which needs a real certificate for a name.

1. Choose a name, e.g. speedtest.your-isp.com, and add its DNS record (A, and AAAA for IPv6) pointing to the router’s public address.

2. Tell the router, and get a certificate from Let’s Encrypt:

   dtvsol speedtest set hostname speedtest.your-isp.com
   dtvsol speedtest certificate noc@your-isp.com --agree-tos

   The router first checks that the name leads to one of its addresses. certbot then opens port 80 for a few seconds so Let’s Encrypt can check the name — port 80 must reach the router from the Internet.

certbot renews the certificate by itself before it ends, and the router loads each new one at once. A warning is raised 14 days before it ends (critical 3 days before).

Other ways (dtvsol speedtest set tls …):

tls	Certificate
certbot	Let’s Encrypt through certbot, for the hostname (above).
file	Your own: dtvsol speedtest set cert /path/fullchain.pem and set key /path/privkey.pem. The router copies it for the server and loads a new one when the file changes.
letsencrypt	Ookla’s own Let’s Encrypt. It works only once the server is registered with Ookla; until then Ookla’s certificate server refuses it and the server uses a self-signed certificate.
none	No certificate of yours: the server uses a self-signed one.

dtvsol speedtest shows which certificate the server uses now.

Show it on speedtest.net

Ookla lists a server only after its owner registers it: sign in at account.ookla.com, open Speedtest server hosting, and add the server with its hostname and port 8080. Ookla checks it and lists it. This is done with your own Ookla account; the router cannot do it for you.

Settings

dtvsol speedtest set tcp-ports 5060,8080
dtvsol speedtest set udp-ports 5060,8080
dtvsol speedtest set ipv6 on
dtvsol speedtest set domains "*.ookla.com, *.speedtest.net"   # who may test (* = everyone)
dtvsol speedtest set max-conn 500                              # connections per IP
dtvsol speedtest set cpu 4
dtvsol speedtest set auto-update on                            # Ookla updates the server by itself
dtvsol speedtest restart
dtvsol speedtest off
dtvsol speedtest remove                                        # Ookla's files gone, settings kept

The monitor’s Settings → Speedtest page shows the same and changes it (admins).

Watched

• The service stopped, or the server not answering its check (/hello on port 8080): an alarm.
• The certificate ending: a warning 14 days before, critical 3 days before.
• Its settings file changed by hand: a drift alarm (dtvsol speedtest restart writes it again).