On 2/3/2023 4:54 AM, Michael Richardson via Bloat wrote:
A new network namespace would certainly work, but it may be unmanageable
overkill.
What you probably need are policy-based routes, which you can establish
statically and then --source ought to work.
That's exactly what turned out to be
Kenneth Porter via Bloat wrote:
> script in /etc/cron.hourly or a systemd timer unit). speedtest-cli
> accepts a --source option but it wants to always route through the WAN
> link set to the default route when I specify the addresses of the other
> two. From googling around it
On Thu, Feb 02, 2023 at 10:15:23AM -0500, Paul Tagliamonte wrote:
> [... stuff ...]
Additional note: the nonfree / closed source speedtest cli binary downloadable
at no cost at https://www.speedtest.net/apps/cli contains a `-i` flag for
binding to a specific interface, which means you don't have
I wasn't going to reply, since I figured others would get here first
with more constructive notes; but since I don't see any, here's some
pointers, but alas, not anything concrete; a lot is still left as an
exercise to the reader. Sorry about that.
Sorry this is a bit long, i'm going to try to
I'm trying to get my head around how to run speedtest-cli on a Rocky 8
box (RHEL8 respin) with LAN and three WAN connections. I want to run
speedtest-cli on all the WAN links to test each, and run the tests
from a timer to watch the speeds throughout the day (eg. a symlink to
a test script in
