arevindh
Unclear selection between testing solutions
Hello,
I noticed that the measured bandwidth has decreased a lot in the last few weeks. I tested with other devices on my network that were not reporting the same values.
After a while, I discovered that the module was using the librespeed CLI instead of the Ookla CLI tool. I removed this tool and the reported value went back to normal.
For some reason, the librespeed-cli tool was reinstalled the next day and the reported values became incorrect again.
See screenshot below.
Selecting the "official" Speedtest CLI has no effect. I was forced to remove the /usr/bin/speedtest binary to force the use of the official CLI.
❓ Question: Can you explain how to make sure the correct CLI is used? ℹ️ Information: the actual bandwidth is 5 Gbps (Up and Down). As PiHole is installed on a rPi4 with a USB stick, the measured bandwidth is capped at 300Mbps due to hardware limitations. In any case, values oscillating around 150Mbps are not correct values.
Hi, thanks for reporting this bug! I think I caused it a few months ago, when I last refactored some code. I'll look into the issue soon.
I have a similar issue where the speedtest binary (sivel) get changed to libre-speedtest. Not sure what the trigger action that causes this. The libre-speedtest results are very low, most likely due to the speedtest server locations (there are not many to select from, unlike the official/sivel server list). I have to replace the /usr/bin/speedtest binary with the sivel speedtest-cli binary to restore sivel speedtest option, checking the radio button does not make the change stick beyond the first run.
Right now the speedtests switch when your selected one fails to run. I initially designed it this way because I noticed Ookla's servers sometimes have network issues and thought it better to show some result than nothing. But I do plan on adding a "Lock" option to prevent that behavior!