From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 8EF3E3CB37 for ; Fri, 3 Feb 2023 09:38:31 -0500 (EST) Received: from dyas.sandelman.ca (unknown [109.190.253.13]) by relay.sandelman.ca (Postfix) with ESMTPS id 744211F4C3; Fri, 3 Feb 2023 14:38:30 +0000 (UTC) Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 8EDECA1E62; Fri, 3 Feb 2023 07:54:44 -0500 (EST) Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 8CA10A1E5C; Fri, 3 Feb 2023 13:54:44 +0100 (CET) From: Michael Richardson To: Kenneth Porter , Bufferbloat Mailing List In-reply-to: <2DD7056F81C7C7313FBA93EA@[10.96.7.39]> References: <2DD7056F81C7C7313FBA93EA@[10.96.7.39]> Comments: In-reply-to Kenneth Porter via Bloat message dated "Wed, 01 Feb 2023 12:20:56 -0800." X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Date: Fri, 03 Feb 2023 13:54:44 +0100 Message-ID: <2027204.1675428884@dyas> Subject: Re: [Bloat] speedtest-cli on multihomed gateway X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Feb 2023 14:38:31 -0000 --=-=-= Content-Type: text/plain 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 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. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAmPdBBQACgkQlUzhVv38 QpC0DAgAg9Jt1jC9kJ+O1qMZ/FLvLRKa0Jc5wM+qsfi1SRenlUVBxQtsEwCDjJ1F +KcgXAdhUlPqxXd+oIeZLynXr7LnwmvjYF5Z1TTh6BolaJxn0BbOyVg6m0tAUcje 2HepahQccn/bkVwt+9o6Bwf7R8uC8AwMVW03lImTCO00xo7ao91ukRc91+nY3fe8 GUDfbUtK+7SQSzNQoITufSRVPECINptVMfaFcmWaqerEBY624D0yJ1L0dTtjAE3P 19p0oTtOUb5vpL3Hvtmgq34kbPy8ARunb4njWCkaxXQaSzEROP4oxXpRj+xkXAUJ 5lL0fNAs4SHgAwrFJrlqm4wvIfmQ1A== =i8OM -----END PGP SIGNATURE----- --=-=-=--