Feature Request #1:
Using the Cockpit interface, On the Applications -> Firewall -> Settings there is a Speedtest button. When you click it and it finishes, you only get the option of applying the results to the traffic shaping paramaters. i would like the option to rerun the test from that page, instead of navigating away and back.
Feature Request #2
I would like it to display the URL of the destination machine so i can check results from another Speedtest tool. I don’t know if it a bug, but the ping RTT and the speed are usually a lot slower than when I measure using Speedtest.net from my desktop computer.
Feature Request #3
I would like the ability to specify the target server for the speedtest operation
I am the developer of diagTools in NethGui, AFAIK it is not simply to choose what server you ping, I decided to let the algorithm choose the closest server.
agree for the button to launch again
hard to choose the server destination
the server destination could be find I guess
however I can see a bug of speedtest-cli it download and upload at the same time, when I do it with F33 and another version, it download first then it do the upload test.
This could explain why my upload measure is far low, it should be the same than the download
Installed Packages
Name : speedtest-cli
Arch : noarch
Version : 1.0.2
Release : 1.el7
Size : 111 k
Repo : installed
From repo : nethserver
Summary : Command line interface for testing internet bandwidth
URL : https://github.com/sivel/speedtest-cli
License : ASL 2.0
Description : Command line interface for testing internet bandwidth using speedtest.net
I agree too, we could add a simple “Run again” button.
I don’t know if this is possible, but I don’t see a link from the JSON output posted by @stephdl. If the link is present we can show it with an hover action or something like this.
Still I’m not really a fan of it
I agree with @stephdl is hard to design a good UI for this usage scenario. Also it is out of scope inside this page.
Current package has been imported inside the nethserver-base repo.
If the output of the new package is compatible with the old one (so it doesn’t break Cockpit nor NethGUI), I’m ok for the update.
Sorry… Why “more buttons”?.
1 Button (only) for run the test. First time or more times. During test the button should be grayed or changed text into “(running)”. A notification should be nice while the test is running. Might be useful a way to specify which red interface is object of test?
1 Button for copying data to the Traffic Shaping /data management of the interface