All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: DNAT multiple --to-destination gone: why?
Date: Thu, 10 Jul 2008 00:39:02 -0500	[thread overview]
Message-ID: <4875A076.5090907@riverviewtech.net> (raw)
In-Reply-To: <48759A72.9030503@usa.net>

On 07/10/08 00:13, Josh Cepek wrote:
> Here's a workaround that might do what you seek.  Optionally, you might 
> consider a DNS-RR instead if it makes sense for your needs.

DNS based load balancing is ok, but it is better in theory.  I think 
something like LVS will do a much better job.

> With the statistic match you can create a round-robin that targets each 
> rule in turn.  To do what you seek above you could use this series of 
> rules, with your own additional matches added as required:
> iptables -A PREROUTING -t nat -m statistic --mode nth --every 2 -j DNAT 
> 10.0.0.101-102
> iptables -A PREROUTING -t nat -j DNAT 10.0.0.104-105

I suppose this would work for a fairly static set of destination 
servers.  Seeing as how you would have to re-write the rules if a back 
end server was added or removed, this would be a major PITA if the 
servers were dynamic in nature.

> This is conceptually the same (but simpler than) the following series of 
> rules:
> iptables -A PREROUTING -t nat -m statistic --mode nth --every 4 -j DNAT 
> 10.0.0.101
> iptables -A PREROUTING -t nat -m statistic --mode nth --every 3 -j DNAT 
> 10.0.0.102
> iptables -A PREROUTING -t nat -m statistic --mode nth --every 2 -j DNAT 
> 10.0.0.104
> iptables -A PREROUTING -t nat -j DNAT 10.0.0.105
> 
> Of course, you can continue to add more rules as required.

Ugh.  That does not scale very well at all.  If you want to remove 102 
from above, you would have to re-write all the rules above it.



Grant. . . .

  reply	other threads:[~2008-07-10  5:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10  0:32 DNAT multiple --to-destination gone: why? David Sparks
2008-07-10  5:13 ` Josh Cepek
2008-07-10  5:39   ` Grant Taylor [this message]
2008-07-10  5:52     ` Josh Cepek
2008-07-10 10:03   ` Jan Engelhardt

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=4875A076.5090907@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=netfilter@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.