All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manish Kathuria <manish@tuxspace.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems in Dead Gateway Detection / Failover - Multiple
Date: Fri, 21 Apr 2006 01:49:52 +0000	[thread overview]
Message-ID: <44483A0A.50107@tuxspace.com> (raw)
In-Reply-To: <43D8CEAE.3010006@tuxspace.com>

Eduardo Fernández wrote:
> Hi!
> 
> Did you finally write a script for dead gateway detection beyond first
> hop? Did you find any other solution to this problem? I'm quite
> interested and I bet other multipath users here are interested too.
> 
> My linux router has 10 dsl links (adding 15 more in short), when one
> of the dsl routers goes down the kernel does not always notice. Don't
> know why. Also, if a dsl route is up but the internet link is down
> dead gateway detection doesn't work either.
> 
> Thanks!
> 
> Edu
> 
> 
If you follow the nano.txt procedure and apply the patches, it works 
perfectly as long as the first hop is dead. But to ensure failover, when 
  connectivity goes down at any of the hops, you can use the nano.txt 
for configuring the interfaces and multipath routes (call it default 
configuration) and also run a script in the background to modify the 
routes as described below.

1. Periodically keep on checking if a remote host is reachable from each 
of the gateways by pinging it after every n seconds.

2. If the remote host is not reachable after a number of tries (which 
you can decide according to your own specific situation) from a 
particular gateway, remove that route. If you have just two internet 
links, there would be only one gateway left. But if you have more than 
two links alive you can again define multipath routes with appropriate 
weights for the active gateways. The possible combinations will increase 
exponentially with the increase in number of internet links so you will 
have to factor is all the cases in the script.

3. Restore the default configuration when the remote host is reachable 
from all the gateways.

I am not too sure how its going to behave with 10 links because if the 
links are not so stable it will result in very frequent changes.

--
Manish Kathuria
http://www.tuxspace.com /

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2006-04-21  1:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 13:41 [LARTC] Problems in Dead Gateway Detection / Failover - Multiple Manish Kathuria
2006-01-29 19:50 ` [LARTC] Problems in Dead Gateway Detection / Failover - gypsy
2006-01-30  3:50 ` Manish Kathuria
2006-04-15 13:58 ` [LARTC] Problems in Dead Gateway Detection / Failover - Multiple Eduardo Fernández
2006-04-17  7:14 ` Re:[LARTC] Problems in Dead Gateway Detection / Failover - Shashikant Mundlik
2006-04-17 14:01 ` [LARTC] Problems in Dead Gateway Detection / Failover Alessandro Ren
2006-04-17 15:16 ` Alessandro Ren
2006-04-17 15:22 ` Shashikant Mundlik
2006-04-17 15:52 ` Shashikant Mundlik
2006-04-17 16:30 ` [LARTC] Problems in Dead Gateway Detection / LinuXKiD
2006-04-17 17:11 ` [LARTC] Problems in Dead Gateway Detection / Failover Alessandro Ren
2006-04-21  1:49 ` Manish Kathuria [this message]

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=44483A0A.50107@tuxspace.com \
    --to=manish@tuxspace.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.