From: Bartek Krajnik <bartek@bicom.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] load balancing without NAT
Date: Thu, 06 Feb 2003 11:03:21 +0000 [thread overview]
Message-ID: <marc-lartc-104452947503772@msgid-missing> (raw)
I have eth0 (isp1, internet), eth1 (isp2, internet) and eth2 for my LAN
eth0 (isp1)
\
Linux - eth2 (LAN)
/
eth1 (isp2)
I need for every connection (not packet) load balancing - TCP sessions must be kept.
For example: first connection from LAN goes through eth0, second through eth1, third through eth0 ...
I can't change anything on the other site of eth0 and eth1.
This explains idea (but is with NAT - I need without):
http://www.linuxvirtualserver.org/~julian/nano.txt
--
GPG-Key:
http://www.bartek.bicom.pl/public_key.txt
pub 1024D/948DE45D 2002-12-12 Bartek Krajnik <bartek@bicom.pl>
Primary key fingerprint: 95E9 8E2D 1801 7864 2244 6EAA 03E5 764D 948D E45D
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-02-06 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 11:03 Bartek Krajnik [this message]
2003-02-06 16:27 ` [LARTC] load balancing without NAT Stef Coene
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-104452947503772@msgid-missing \
--to=bartek@bicom.pl \
--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