From: Michael Richardson <mcr@sandelman.ca>
To: Kenneth Porter <shiva@sewingwitch.com>,
Bufferbloat Mailing List <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] speedtest-cli on multihomed gateway
Date: Fri, 03 Feb 2023 13:54:44 +0100 [thread overview]
Message-ID: <2027204.1675428884@dyas> (raw)
In-Reply-To: <2DD7056F81C7C7313FBA93EA@[10.96.7.39]>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
Kenneth Porter via Bloat <bloat@lists.bufferbloat.net> 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 looks like I want to run it in a "network
> namespace" but I haven't figured out how to make that work.
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.
ip route now has a "from" option, but it doesn't always work in my
experience. The old way is to do:
ip rule add from A.B.C.D/32 table 123
ip route add default via 192.0.1.2 table 123
I put these into "up" statements into my /etc/network/interfaes, but you say
you are running RHEL... I'm sure that there is a netplan way.
This also means that if you have a monitoring system elsewhere (smokeping or
something), and you ping each interface, then it will reply on that
interface.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2023-02-03 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 20:20 Kenneth Porter
2023-02-02 15:15 ` Paul Tagliamonte
2023-02-02 15:36 ` Paul Tagliamonte
2023-02-03 12:54 ` Michael Richardson [this message]
2023-02-03 23:20 ` Kenneth Porter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2027204.1675428884@dyas \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=shiva@sewingwitch.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox