From: "Sushil Suresh" <sushil@svw.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Will advanced linux routing help me
Date: Fri, 27 Apr 2001 10:49:36 +0000 [thread overview]
Message-ID: <marc-lartc-98836784420391@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98816711030206@msgid-missing>
Hi,
At the moment we are using trace and ping to check the availability of a
particular site, and the status of a particular ISP
The problem faced in making use of these commands in a script is that, they
may fail in case of congestion and may be misunderstood as failure of a
particular ISP.
Also how and why do you flush the route cache?
with regards,
Sushil Suresh
----- Original Message -----
From: Arthur van Leeuwen <arthurvl@sci.kun.nl>
To: Sushil Suresh <sushil@svw.com>
Cc: <lartc@mailman.ds9a.nl>
Sent: Wednesday, April 25, 2001 1:09 PM
Subject: Re: [LARTC] Will advanced linux routing help me
> On Wed, 25 Apr 2001, Sushil Suresh wrote:
>
> [snip, automatic rerouting when interfaces are downed]
>
> > Is there any means to automise the whole process. The effective aim
> > is to utilize the most of all the isps that are available at a moment
> > of time.
>
> > ( At the moment we attain this via static routing and we have one
> > personal monitoring this round the clock, in case a rerouting is
necessary )
>
> Okay, the thing to do is to figure out what this person is doing to check
if
> the links are up. Once you know this, you put that knowledge into a script
> that checks if the link is up and run that script from cron. Depending on
> the status of the uplinks you then let the script select one of the
possible
> static routings and enable it. (Rebuilding routing tables barely hurts
> reliability, *especially* if you do not flush the route cache).
>
> Hope this helps.
>
> Doei, Arthur. (The tricky part is the link-state monitoring... at the
TCP/IP
> level this is theoretically impossible...)
>
> --
> /\ / | arthurvl@sci.kun.nl | Work like you don't need the
money
> /__\ / | A friend is someone with whom | Love like you have never been
hurt
> / \/__ | you can dare to be yourself | Dance like there's nobody
watching
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-04-27 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 2:51 [LARTC] Will advanced linux routing help me Sushil Suresh
2001-04-25 7:39 ` Arthur van Leeuwen
2001-04-25 12:50 ` Ramin Alidousti
2001-04-27 10:41 ` Sushil Suresh
2001-04-27 10:49 ` Sushil Suresh [this message]
2001-04-27 11:41 ` Arthur van Leeuwen
2001-04-27 13:30 ` Ramin Alidousti
2001-04-27 13:32 ` Ramin Alidousti
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-98836784420391@msgid-missing \
--to=sushil@svw.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.