All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent AE Scott <lartc@codex.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] question re: dead gateway detection
Date: Wed, 27 Mar 2002 13:15:48 +0000	[thread overview]
Message-ID: <marc-lartc-101723500432185@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101722239517873@msgid-missing>

Thomas Vander Stichele(thomas@urgent.rug.ac.be)@Wed, Mar 27, 2002 at 10:45:10AM +0100:
> Hi,
> 
> I've followed the instructions in the nano document, and apart from my own 
> ISP trouble, it seems to work fine.  I have a question about the dgd 
> however.
> 
> The dgd works on the actual gateway, but in my experience it seems that 
> most problems can be expected a few hops down the route, not on the 
> gateway.  One of those two gateways is located here anyway, so if that 
> goes down then chances are other stuff is wrong as well ;)
> 
> So my question is: is there some way that I can detect that the actual 
> route to the net is unusable, even though the gateway is up ? If not, when 
> either one of the lines is down, users will notice they're not getting a 
> connection randomly, depending on what gateway is used for that 
> connection.
> 
> Thomas

It sounds to me like you need something which is proactively monitoring
your network health/status.  The points in the network your referring
to, are not under your sirect control, so there's not a lot tc/ip can
directly do to solve your problem.

but with some clever scripting, you could attempt to detect a fault in
the network, and take appropriate action.  such as delete the faulty
route for all the clients that were using it, and forec them onto the
other route.   you'll still need to be able to test the dead route from
the box, such that you can activate again, once its working.

i hope i understood the problem correctly, and havent gone off on one.

-vince



-- 
PGP key:  http://codex.net/pgp/pgp.asc

 Computers make very fast, very accurate mistakes.

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

  reply	other threads:[~2002-03-27 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27  9:45 [LARTC] question re: dead gateway detection Thomas Vander Stichele
2002-03-27 13:15 ` Vincent AE Scott [this message]
2002-03-27 13:59 ` Thomas Vander Stichele
2002-03-27 16:22 ` Steele, Tom
2002-03-29 10:26 ` Thomas Vander Stichele

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-101723500432185@msgid-missing \
    --to=lartc@codex.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.