From: "Greg Scott" <GregScott@InfraSupportEtc.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Load balancing
Date: Wed, 26 Jun 2002 21:52:32 +0000 [thread overview]
Message-ID: <marc-lartc-102512835209719@msgid-missing> (raw)
I am trying to figure out how to do this: I've tried the howto but just become
hopelessly confused. (I don' think this is a problem in the howto, it's a problem
with my comprehension.)
Anyway, here's the scenario:
Internal Linux Router/ 4 - T1 circuits to Another
Networks Firewall the Internet Internet circuit
| | | | | | | | | |
+-----------------+ | | +------------+------+------+------+---------------+
--------------------+ |
------------------------+
There are really three internal networks for various departments. The router/firewall
will have 4 NICs.
For one of the internal departments, I want the router to load-balance outbound
packets among those 4 T1 circuits, which will be connected to Cisco (I think)
routers. I want the other departments to all share that other Internet circuit.
And I need the ability to change this policy at will, so I can let other departments
use the combined T1s as needed.
I think I can figure out how to route based on the source network, that all makes
sense in the how-to. I can set up different routing tables based on the source IP
address/network. It's the load balancing that is making me crazy - how do I put
together a load-balancing mechanism for those combined T1s that makes sense?
Any advice or pointers?
thanks
- Greg Scott
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-06-26 21:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 21:52 Greg Scott [this message]
2002-06-28 5:27 ` [LARTC] Load balancing William L. Thomson Jr.
2002-07-04 14:52 ` bert hubert
2003-02-19 19:27 ` Paul English
2003-05-08 11:50 ` [LARTC] load balancing Lucas Aimaretto
2003-05-08 13:08 ` Sjaak Nabuurs
2003-05-09 15:44 ` Víctor Nuño
2003-05-09 15:55 ` Martin A. Brown
2003-11-28 1:41 ` Евгени Гечев
2003-11-28 12:38 ` Ivo Vachkov
2003-11-28 18:47 ` Evgeni Gechev
2003-11-28 19:02 ` Artūras Šlajus
2003-11-28 23:22 ` Ivo Vachkov
2004-07-26 1:35 ` [LARTC] Load Balancing XMundo - Soporte Tecnico
2004-07-26 23:58 ` XMundo - Soporte Tecnico
2004-09-15 17:10 ` [LARTC] load balancing pbruna
2004-09-17 3:21 ` Glen Mabey
2005-01-12 21:15 ` Antonio Pérez
2005-11-16 20:13 ` comp.techs
2006-10-13 8:54 ` Indunil Jayasooriya
2006-10-13 8:55 ` Indunil Jayasooriya
2006-12-13 22:07 ` Charlie Meyer
2006-12-13 22:42 ` Grant Taylor
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-102512835209719@msgid-missing \
--to=gregscott@infrasupportetc.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.