From: Patrick McHardy <kaber@trash.net>
To: Denys <denys@visp.net.lb>
Cc: wijata@nec-labs.com, Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 8325] New: -j REDIRECT --to-ports 1000-1009, always first choosen
Date: Mon, 16 Apr 2007 07:52:06 +0200 [thread overview]
Message-ID: <46230F06.4020201@trash.net> (raw)
In-Reply-To: <20070416054247.M18950@visp.net.lb>
Denys wrote:
> On Mon, 16 Apr 2007 07:30:33 +0200, Patrick McHardy wrote
>
>>That makes sense with using multiple IPs (and we support doing that),
>>but whats the point of load-balancing to differenet *ports*?
>
>
> Easy - for example i have my own TCP acceleration solution, which is using
> REDIRECT, then getsockopt/SO_ORIGINAL_DST to get original IP, then forwarding
> to compressed tunnel, stripping unneeded bytes (oh, my expensive satellite
> bandwidth). This way for example i can do some kind load-balancing for
> satellite bandwidth.
That sounds rather hackish, you might as well do it in your application.
I just noticed we don't accept the random option for DNAT/REDIRECT yet,
but that is easily fixed (I'll queue a patch for 2.6.22). Then this
will work and select ports from the range randomly:
iptables -t nat -A INPUT .. -j REDIRECT --to-ports 1000:1010 --random
prev parent reply other threads:[~2007-04-16 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200704132053.l3DKrC9X000466@fire-2.osdl.org>
2007-04-13 21:47 ` [Bugme-new] [Bug 8325] New: -j REDIRECT --to-ports 1000-1009, always first choosen Andrew Morton
2007-04-16 5:12 ` Patrick McHardy
2007-04-16 5:26 ` Denys
2007-04-16 5:30 ` Patrick McHardy
2007-04-16 5:45 ` Denys
2007-04-16 5:52 ` Patrick McHardy [this message]
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=46230F06.4020201@trash.net \
--to=kaber@trash.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
--cc=wijata@nec-labs.com \
/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.