From: Kenneth Kalmer <kenneth.kalmer@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Spill over
Date: Sat, 23 Apr 2005 21:34:33 +0000 [thread overview]
Message-ID: <fad9d484050423143460593cb9@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1048 bytes --]
List
I need some help, advice or just a starting point on the following
situation:
Link A - 64kbps leased line
Link B - 512kbps ADSL line
Is it possible to have Link A saturated constantly and have the excess
traffic "spill over" onto Link B? I know it's possible to have packets sent
down links in a round-robin fashion and I've read in the howto on load
sharing over multiple interfaces (
http://lartc.org/howto/lartc.loadshare.html), but I do not have control over
the termination of the link at the ISP's (two different one as well). Also
note that splitting different protocols over each of these links are not
possible in our case.
Reason being, Link A is a more reliable and more expensive link, so I need
to over-use it's capacity if it we're, and use the cheaper ADSL (link B)
offering to keep al services running when the leased line (A) is saturated.
Any tips, suggestions and comments would be welcomed.
Regards
--
Kenneth Kalmer
kenneth.kalmer@gmail.com
http://opensourcery.blogspot.com
[-- Attachment #1.2: Type: text/html, Size: 1263 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2005-04-23 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 21:34 Kenneth Kalmer [this message]
2005-04-23 22:11 ` [LARTC] Spill over Taylor Grant
2005-04-23 23:18 ` Chris Bennett
2005-04-25 7:48 ` Kenneth Kalmer
2005-04-25 15:43 ` Taylor, Grant
2005-04-25 21:56 ` Chris Bennett
2005-05-04 11:11 ` Kenneth Kalmer
2005-05-04 21:12 ` Kenneth Kalmer
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=fad9d484050423143460593cb9@mail.gmail.com \
--to=kenneth.kalmer@gmail.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.