From: Christoph Simon <ciccio@kiosknet.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] many ways to do load balancing (or not?)
Date: Fri, 22 Nov 2002 13:00:30 +0000 [thread overview]
Message-ID: <marc-lartc-103797010800813@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103788125614081@msgid-missing>
On Fri, 22 Nov 2002 10:30:35 -0200
Andreas Hasenack <andreas@conectiva.com.br> wrote:
> Em Thu, Nov 21, 2002 at 08:55:05PM -0200, Christoph Simon escreveu:
> > My understanding is, that for equalize to work, all lines must go to
> > the same point and that must not be the end point. Also, this same
> > point must implement the equalize very much the same way.
>
> What is it that you call a "point" here (destination)? The same ISP? The
> same network?
>
> I understand that it should be the same ISP because of egress filtering,
> that is, one ISP should block packets with a source address that doesn't
> belong to the ISP supplying the link.
I was thinking of a configuration like:
Satelite Main-Office
-> ISP1 -m-
LAN1 -> ISP2 -m- ISPx -> linux-router2 -> ISP-BIG ->
-> ISP3 -m-
If I have an office with one big Internet tube (e.g., MBs), I can put
"linux-router2" there. Then all satelite offices could use one or more
modems to reach this router. That linux-router2 would NAT everybody
coming from the modems and forward the packets to ISP-BIG. Nobody in
LAN1 would even attempt to reach linux-router2, which is the last
point where their actually source addresses are known. With equalize
this should allow for a packetwise loadbalancing to increase the
effective bandwidth even for a single file transfer between a host in
LAN1 and ISP-BIG. In this configuration, all modem lines go finally to
one point (linux-router2) and that is not the endpoint. In fact, all
internal clients would use linux-router2 as the default gateway. No
cooperation of any ISP is required.
This configuration makes sense if LAN1 and linux-router2 are in
different cities and either LAN1 has no other reliable choice than
modems or wants redundancy. ISP-BIG also needs to be cheap and
reliable enough for this to make sense.
As I said before, I didn't play too much with equalize, but can't see
a essencially different scenario for a packet-wise loadbalancing.
--
Christoph Simon
ciccio@kiosknet.com.br
---
^X^C
q
quit
:q
^C
end
x
exit
ZZ
^D
?
help
.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-22 13:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 12:19 [LARTC] many ways to do load balancing (or not?) Andreas Hasenack
2002-11-21 17:46 ` Ashok N N
2002-11-21 19:11 ` Andreas Hasenack
2002-11-21 20:00 ` Ramin Alidousti
2002-11-21 22:20 ` William L. Thomson Jr.
2002-11-21 22:55 ` Christoph Simon
2002-11-21 23:41 ` Christoph Simon
2002-11-22 0:06 ` William L. Thomson Jr.
2002-11-22 0:24 ` William L. Thomson Jr.
2002-11-22 1:17 ` Ashok N N
2002-11-22 12:28 ` Andreas Hasenack
2002-11-22 12:30 ` Andreas Hasenack
2002-11-22 12:39 ` Andreas Hasenack
2002-11-22 12:41 ` Andreas Hasenack
2002-11-22 13:00 ` Christoph Simon [this message]
2002-11-22 13:26 ` Vincent Jaussaud
2002-11-22 18:05 ` William L. Thomson Jr.
2002-11-22 18:21 ` William L. Thomson Jr.
2002-11-22 18:37 ` William L. Thomson Jr.
2002-11-22 18:47 ` William L. Thomson Jr.
2002-11-22 20:34 ` Andreas Hasenack
2002-11-25 13:20 ` Vincent Jaussaud
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-103797010800813@msgid-missing \
--to=ciccio@kiosknet.com.br \
--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