From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Split access, load balancing AND forwarding: HOW?
Date: Fri, 23 Feb 2007 07:23:42 +0000 [thread overview]
Message-ID: <000101c7571b$ee2eda90$02bca8c0@freelance> (raw)
In-Reply-To: <Pine.LNX.4.64.0702211529590.9170@dellareas.intoweb.co.za>
From: "Luciano Ruete" <luciano@lugmen.org.ar>
>
> This solution works in theory and in practice, so plz, get your hands dirty
> before you post your next great idea.
>
I understand your explanation fully but believe me I also have got
hand-on experience with using the alternative, ie
1. I don't use multipath weight routing.
2. I use PREROUTING all the way, ie I don't use POSTROUTING.
Instead, I use iptables 'recent' and 'statistics'/'random' match to achieve
load sharing.
I have use this for many years already, believe me I am not theoretical.
It's just a matter of different ways to doing things. If you search the web
it will come upon many others using the same method I used.
Cheers
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-02-23 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 14:10 [LARTC] Split access, load balancing AND forwarding: HOW? Andrew McGill
2007-02-22 2:16 ` Luciano Ruete
2007-02-22 2:58 ` Ming-Ching Tiew
2007-02-22 4:57 ` Ming-Ching Tiew
2007-02-23 2:54 ` Luciano Ruete
2007-02-23 3:06 ` Luciano Ruete
2007-02-23 3:48 ` Roy Orpiano
2007-02-23 7:23 ` Ming-Ching Tiew [this message]
2007-02-23 18:40 ` Alex Samad
2007-02-23 23:59 ` Ming-Ching Tiew
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='000101c7571b$ee2eda90$02bca8c0@freelance' \
--to=mingching.tiew@redtone.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.