Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] load balancing
Date: Fri, 09 May 2003 15:55:39 +0000	[thread overview]
Message-ID: <marc-lartc-105249588605509@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102512835209719@msgid-missing>

Hello Víctor,

 : I tried this and it works when an interface goes down, but how can I do
 : if it's not an interface but one of these gateways that goes down? I
 : would like that in this case, the apropriate "nexthop" drops too, so my
 : traffic goes through the other two, and when that fallen gateway is
 : once again alive, the "nexthop" comes alive too, so it's once again
 : used. How can I do this?

You probably should try out the dead gateway detection patches by Julian
Anastasov [1] documented here [2].

I have not yet used the DGD patches, but my understanding is that they'll
detect unreachability of the nexthop and mark a route as dead until the
nexthop becomes reachable again.

As I'm sure you can imagine, it's much more difficult to identify problems
further upstream--and that's what dynamic routing protocols are for,
anyway.

 : >/sbin/ip route add equalize \
 : >            nexthop via $ADSL_GW1 dev $ADSL_IFACE1 weight 1\
 : >            nexthop via $ADSL_GW2 dev $ADSL_IFACE2 weight 1\
 : >            nexthop via $ADSL_GW3 dev $ADSL_IFACE3 weight 1

Best of luck,

-Martin

 [1]  http://www.ssi.bg/~ja/#routes
 [2]  http://www.ssi.bg/~ja/dgd-usage.txt

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-05-09 15:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26 21:52 [LARTC] Load balancing Greg Scott
2002-06-28  5:27 ` William L. Thomson Jr.
2002-07-04 14:52 ` bert hubert
2003-02-19 19:27 ` Paul English
2003-05-08 11:50 ` [LARTC] load balancing Lucas Aimaretto
2003-05-08 13:08 ` Sjaak Nabuurs
2003-05-09 15:44 ` Víctor Nuño
2003-05-09 15:55 ` Martin A. Brown [this message]
2003-11-28  1:41 ` Евгени Гечев
2003-11-28 12:38 ` Ivo Vachkov
2003-11-28 18:47 ` Evgeni Gechev
2003-11-28 19:02 ` Artūras Šlajus
2003-11-28 23:22 ` Ivo Vachkov
2004-07-26  1:35 ` [LARTC] Load Balancing XMundo - Soporte Tecnico
2004-07-26 23:58 ` XMundo - Soporte Tecnico
2004-09-15 17:10 ` [LARTC] load balancing pbruna
2004-09-17  3:21 ` Glen Mabey
2005-01-12 21:15 ` Antonio Pérez
2005-11-16 20:13 ` comp.techs
2006-10-13  8:54 ` Indunil Jayasooriya
2006-10-13  8:55 ` Indunil Jayasooriya
2006-12-13 22:07 ` Charlie Meyer
2006-12-13 22:42 ` Grant Taylor

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-105249588605509@msgid-missing \
    --to=mabrown-lartc@securepipe.com \
    --cc=lartc@vger.kernel.org \
    /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