Speedtest-Tracker VS dnscrypt-proxy

here's the top two results if you search for "open speed test nginx reverse proxy": https://github.com/librespeed/speedtest/wiki/Reverse-proxy-with-Nginx https://github.com/henrywhitaker3/Speedtest-Tracker/issues/924

I have a WFH job but live in a rural area where the internet service is frequently unreliable. I'd like to monitor and log outage incidents (e.g. time of incident, duration) so that I can provide that data to my local service provider and get some real assistance in solving the problem. I have been using a small container app called SpeedTest Tracker which helps, but it's fairly heavyweight for what I want to accomplish. I'd like to (1) get longer historical data (e.g. ~90 days reporting), (2) get more granular reporting intervals (e.g. every 5-15min), and (3) more lightweight in the test payload (e.g. simple ping as opposed to large data transfer).

https://github.com/henrywhitaker3/Speedtest-Tracker this is what I use to track my internets up and down speeds.

oh if it's the actual speed you're interested in... see on my dashboard there are two speedtest panels in the 'monitoring' section? those are two instances of this - https://github.com/henrywhitaker3/Speedtest-Tracker - one running on each machine and they test the speed at regular intervals and keep a log.

Never mind -- Found it, https://github.com/henrywhitaker3/Speedtest-Tracker for anyone interested.

Not sure if this is what he's using but I use https://github.com/henrywhitaker3/Speedtest-Tracker

I would also add Speedtest-Tracker so you can make sure your getting speeds for which you pay for, It keeps historical data so you can go back a bit, I have my testing every 30 minutes. The default is once an hour.

Essentially I'm looking for something similar to this Speedtest Tracker, but where I can specify the iperf3 server(s) to test against.

There is more than one way to do this but I have decided to use dnscrypt-proxy. We will not be using dnscrypt for the dnscrypt protocol though you could elect to use that as the underlying DNS protocol. dnscrypt-proxy lets's us use a SOCKS5 proxy through which the DNS queries will be sent. We will use a Tor SOCKS5 proxy here. You can choose which protocols should be enabled and which ones should be disabled. There are two points:

I tried installing the RPM from the Fedora repos but it's out-of-date and there were no instructions on how to get it operational, so I went with the manual approach as per their wiki: https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Installation-linux

This is awesome, thanks -- going to look into that now. I found SmartDNS interesting and thought I would share it, it's pretty simple to setup. I can see why it's Chinese focused, they have "interesting" internet access over there :-).

I have been looking into DNS quite a bit lately (Unbound, etc), as DNS lookup performance has been pretty subpar lately. I'm in Perth, Australia, and we're pretty remote so our latency is meh at best, and Cloudflare performance has been all over the shop lately, I think they're having issues in WA). DNS can also cause really routing issues here sometimes as we get better latency to Singapore than Sydney, so we might get shunted off to SG.

I've also been using dnscrypt-proxy2 (https://github.com/DNSCrypt/dnscrypt-proxy) for a while, but the above issues with Cloudflares DNS is what triggered me to look into other options.

I use a min-cache-ttl of 15 minutes, which seems to work well.

Thank you for sharing this tip about, looking into this now :).

Sure. I run dnscrypt_proxy behind a pihole. https://github.com/DNSCrypt/dnscrypt-proxy