All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] DGD patch not detecting dead gateway
Date: Sat, 20 Jan 2007 04:13:06 +0000	[thread overview]
Message-ID: <45B196D2.3040802@riverviewtech.net> (raw)
In-Reply-To: <7fe14e000701182100l5b1474eai853a0077c821a835@mail.gmail.com>

On 01/19/07 12:45, Manish Kathuria wrote:
> My experience has been mixed. The patch worked very well in many cases
> but in some it worked only if the first hop gateway was down and not
> any of the subsequent hops. So as you mentioned its happening since it
> can ping the switch / modem, it thinks the link is good. You can make
> a script which will keep on running in the background and check it the
> links are up or not and if any of the links is down, it can change the
> default route and provide a failover.

I have been tasked with writing such a script.  In my scenario, I'm 
taking it a bit further though.  I am planing on having my script test 
the actual service that I'm trying to connect to.  I.e. connect to port 
80 and request a page.  I'm having to go this route because I've had 
sporadic MTU issues in one of our (primary) paths.  The provider is 
suppose to be repairing the problem, however I need a solution before 
that can happen.

I am planing on writing a small daemon, probably in Perl, that will run 
the tests.  What I don't have a good way to do is alter the routing 
tables, short of shelling out and running ip directly.  I would like to 
know if any one knows of any other way to alter the routing tables / 
rules short of calling a shell command.



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

  parent reply	other threads:[~2007-01-20  4:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19  5:00 [LARTC] DGD patch not detecting dead gateway Tom Lobato
2007-01-19 18:57 ` Manish Kathuria
2007-01-20  4:13 ` Grant Taylor [this message]
2007-01-23  0:40 ` Tom Lobato
2007-01-27 14:52 ` Manish Kathuria
2007-01-27 16:24 ` Manish Kathuria
2007-01-28 16:12 ` Tom Lobato
2007-01-28 16:47 ` Manish Kathuria
2007-02-07 23:52 ` Tom Lobato
2007-02-08 19:19 ` Manish Kathuria
2007-02-12 11:34 ` Tom Lobato
2007-05-11  2:56 ` Salim S I
2007-05-14  5:47 ` Manish Kathuria
2007-05-14  5:59 ` Salim S I

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=45B196D2.3040802@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --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.