From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Picton Date: Wed, 14 Mar 2007 12:44:42 +0000 Subject: Re: [LARTC] DGD of upstream routers Message-Id: <1173876282.18504.13.camel@localhost> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============0111946997==" List-Id: References: <45F03E67.6040604@tangent.co.za> In-Reply-To: <45F03E67.6040604@tangent.co.za> To: lartc@vger.kernel.org --===============0111946997== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-pC2vxYJ2auZZ3BlzeH+L" --=-pC2vxYJ2auZZ3BlzeH+L Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi all I have seen the below question asked a few times, but not seen any answers. Is this because 1) it is not possible 2) It is really simple and I shouldn't even be asking the question :) Can somebody please enlighten me. Thanks Chris On Thu, 2007-03-08 at 18:48 +0200, Chris Picton wrote: > Hi >=20 > I have read various info, and mailing list archives, but have not found=20 > an answer to the following. >=20 > I have a few servers with configurations similar to the following: >=20 > They each have multiple uplinks to the Internet, and a sample config is=20 > as follows: >=20 > eth1 is 192.168.0.1, connected to 192.168.0.2 > eth2 is 192.168.1.1, connected to 192.168.1.2 >=20 > My default route looks like: > ip route add scope global equalize nexthop via 192.168.0.2 dev eth1 \=20 > weight 1 nexthop via 192.168.1.2 dev eth2 weight 1 >=20 > If one line goes down, I would like the second to be used exclusively=20 > until the first comes back up >=20 > However, the IPs 192.168.0.2 and 192.168.1.2 are always available and=20 > reachable. It is the connection past those devices which may drop. >=20 > Do any of the available options or patches take this into account, or do=20 > I have to write custom ping scripts to try reach remote hosts via each=20 > gateway, and modify the routes if a line appears to be down. >=20 >=20 > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc ---------------------+---------------------------------------------------- Chris Picton | PGP Key ID: 9D28A988 (wwwkeys.pgp.net) Technical Director | PGP Key Fingerprint: Tangent Systems | 2B46 29EA D530 79EC D9EA 3ED0 229D 6DD6 9D28 A988 011 447 8096 | "Quid quid latine dictum sit, altum viditar" chrisp@tangent.co.za | http://www.tangent.co.za/keys/chrisp.asc ---------------------+---------------------------------------------------- --=-pC2vxYJ2auZZ3BlzeH+L Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBF9+46Ip1t1p0oqYgRAijOAJwNXbyB3hYZtdOLTFackentDRvwFwCdHmQU oTusooztt1kjaNO0Nc89A84= =gKJg -----END PGP SIGNATURE----- --=-pC2vxYJ2auZZ3BlzeH+L-- --===============0111946997== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============0111946997==--