From: "hare ram" <hareram@sol.net.in>
To: Daniel Wittenberg <daniel-wittenberg@starken.com>,
Netfilter <netfilter@lists.netfilter.org>
Subject: Re: [SPAM-RATING-1] Re: equalize traffic when link is down
Date: Sat, 8 Mar 2003 16:46:41 +0530 [thread overview]
Message-ID: <04e401c2e564$3328d700$13fcc5cb@Housecall> (raw)
In-Reply-To: 1047109241.1990.85.camel@runabout.noc.starken.com
Yes
you can make some cron job for the testing the both links active or not
if one of the things down, you can clear the route cache
but who ever have been in the cached will be lost
hare
----- Original Message -----
From: "Daniel Wittenberg" <daniel-wittenberg@starken.com>
To: "Netfilter" <netfilter@lists.netfilter.org>
Sent: Saturday, March 08, 2003 1:10 PM
Subject: Re: [SPAM-RATING-1] Re: equalize traffic when link is down
> Ok, makes sense, so if we just drop the cache timeout (don't remember if
> you can configure that or not) then we can adjust the "switch-over" time
> in case the default is too high.
>
> Great, thanks!
> Dan
>
> On Sat, 2003-03-08 at 01:53, hare ram wrote:
> > Hi
> >
> > AFAIK,
> >
> > If the First Link down, the total traffic will move to Other Second
Link,
> > if you are configure and load balancing the Link
> >
> > If you make the static routes , them the traffic will be dead
> >
> > If you made the Loadbalance the both the links,
> > then it will take some time to clear the routecache, once fresh route
> > cache build you will have the fresh routes,
> > so all the traffic will move towards active link.
> >
> >
> > hare
>
>
>
>
next prev parent reply other threads:[~2003-03-08 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 7:06 equalize traffic when link is down Daniel Wittenberg
2003-03-08 7:53 ` hare ram
2003-03-08 7:40 ` [SPAM-RATING-1] " Daniel Wittenberg
2003-03-08 11:16 ` hare ram [this message]
2003-03-08 15:23 ` QoS Franco Antonio Catena
2003-03-08 20:31 ` QoS SBlaze
2003-03-08 22:37 ` IPTABLES so estrange Franco Antonio Catena
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='04e401c2e564$3328d700$13fcc5cb@Housecall' \
--to=hareram@sol.net.in \
--cc=daniel-wittenberg@starken.com \
--cc=netfilter@lists.netfilter.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