packages/utils/librespeed-common/files/librespeed-run, branch master

librespeed-common: measure and schedule per interface

2026-10-28T09:13:45Z

Every result named main.interface, even when the test had gone out another link, so a backup uplink such as LTE could not be measured on its own, and a day's aggregate mixed all links. librespeed-run and ubus start take an optional interface. IPv4 and IPv6 on one device (wan and wan6) count as one link. Each test is bound to the device of its link, and its result names that link. A link with none of its interfaces up is not measured; its failure is shown. The same holds for an interface netifd does not know, such as a disabled one, and for any while netifd does not answer; ubus start refuses these at once. 'librespeed-run --links' and ubus links print the link each interface is recorded under and the links to offer, leaving out a static interface without a gateway such as lan, so a frontend need not repeat the rule. A failure is reported per interface until a result is recorded on its link, or until no configuration names that interface any more. The init script writes one cron line per interface, aggregates are kept per day and interface, and a run that finds another in progress waits up to 3 minutes, as several schedules fire at the same minute, then gives up and records that as the interface's failure. Existing configs, cron lines and history keep working, except that a default interface whose link is down, or that netifd does not know, is no longer measured. Signed-off-by: Josef Schlehofer

librespeed-common: free the lock as soon as a run ends

2026-10-28T09:13:45Z

The traffic sampler of a bound run inherited the lock's descriptor, so its last 'sleep 1' held the lock up to a second after the run ended, and a test started right then was refused as already running. Signed-off-by: Josef Schlehofer

librespeed-common: add measurement backend

2026-09-03T12:53:08Z

Add a common backend for running librespeed-cli measurements on a router. The package provides a locked measurement runner, live progress state, and an rpcd ucode plugin exposing start/stop/status/result/history/config over ubus. Scheduled measurements are managed through cron and can run within a configurable time window. Optional daily aggregation keeps longer-term history compact. Raw measurements are kept in JSONL for a configurable retention period. When persistent archive storage is configured, completed days are reduced to daily min/avg/max values. Signed-off-by: Josef Schlehofer