From: Peter Rabbitson <rabbit@rabbit.us>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Load Balance and SNAT problem.
Date: Wed, 27 Jun 2007 05:54:42 +0000 [thread overview]
Message-ID: <4681FBA2.7000709@rabbit.us> (raw)
In-Reply-To: <7e47206b0706242007q487365d3gb7c12658b9669edd@mail.gmail.com>
Salim S I wrote:
> The caching is per destination and source ip. TOS, fwmark and input
> interface too, if present.
Interesting... It definitely did not work in my scenario though. I am
going to test this again in the near future, and if you are right I will
rest my case.
> Routing with netfilter does not solve cache problems anyway, cache will
> still be present, and it will be consulted before routing tables are
> hit.
This is true for locally generated traffic only. Any incomming/forwarded
traffic can be controlled in the PREROUTING, thus the cache is never
consulted.
> Both solutions work pretty well; there are die-hard fans for both of the
> above approaches. Recent archives of lartc have lot of discussions on
> it.
I am actually simply jealous that some people apparently get it to work
in-kernel, and I can't seem to. My requirements are pretty simple:
o As transparrent as possible DGD, that can detect 2nd and 3rd hop failures
o Robust load balancing - connections are distributed over all available
links, regardless of source and destination, with the possibility of
assigning relative channel priorities
o NAT compatible - link hopping is not an option, traffic with a
specific SRC/DST must stay where it started.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-06-27 5:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 3:07 [LARTC] Load Balance and SNAT problem John Chang
2007-06-25 14:47 ` Grant Taylor
2007-06-25 21:30 ` VladSun
2007-06-26 6:46 ` Peter Rabbitson
2007-06-26 11:36 ` John Chang
2007-06-26 14:37 ` Grant Taylor
2007-06-26 15:04 ` Patrick Brandão
2007-06-26 17:44 ` Peter Rabbitson
2007-06-27 1:24 ` Grant Taylor
2007-06-27 1:51 ` Grant Taylor
2007-06-27 2:07 ` Grant Taylor
2007-06-27 2:22 ` Salim S I
2007-06-27 2:34 ` Grant Taylor
2007-06-27 2:39 ` Grant Taylor
2007-06-27 3:07 ` Salim S I
2007-06-27 3:16 ` Grant Taylor
2007-06-27 5:54 ` Peter Rabbitson [this message]
2007-06-27 6:41 ` Salim S I
2007-06-27 6:43 ` Grant Taylor
2007-06-27 6:58 ` Peter Rabbitson
2007-06-27 7:28 ` Grant Taylor
2007-06-27 7:37 ` Grant Taylor
2007-06-27 7:53 ` Grant Taylor
2007-06-27 7:57 ` Grant Taylor
2007-06-27 8:03 ` Peter Rabbitson
2007-06-27 8:03 ` Grant Taylor
2007-06-27 8:11 ` Grant Taylor
2007-06-27 8:24 ` Grant Taylor
2007-06-27 8:26 ` Grant Taylor
2007-06-27 9:09 ` Peter Rabbitson
2007-06-27 10:19 ` 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=4681FBA2.7000709@rabbit.us \
--to=rabbit@rabbit.us \
--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.