Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "lartc@manchotnetworks.net" <lartc@manchotnetworks.net>
To: lartc@vger.kernel.org
Subject: [LARTC] failover-overload
Date: Mon, 13 Oct 2003 16:28:46 +0000	[thread overview]
Message-ID: <marc-lartc-106606355704441@msgid-missing> (raw)

hi all,

curious if anyone can comment on the existence (or perhaps) non
existence of an overload feature --

when one line to an isp is at its peek, the second line starts getting
the new sessions?

also, i noticed in an earlier thread the keepalive daemon for just
failover (the first line is an adsl, the second and third are vsat) --
given the extra delay that a vsat imposes, i prefer to keep them for an
overload or failover condition. could someone post their cfg from
keepalive and/or comment on its efficacy?

thanks a million

charles






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

                 reply	other threads:[~2003-10-13 16:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-106606355704441@msgid-missing \
    --to=lartc@manchotnetworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox