From: KOVACS Krisztian <hidden@sch.bme.hu>
To: Khoa Nguyen <khoa.coffee@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: SNAT round-robin broken?
Date: Mon, 13 Feb 2006 21:45:24 +0100 [thread overview]
Message-ID: <200602132145.27983@krak> (raw)
In-Reply-To: <3d00e6dc0602130610j3ccc1c2cseaf06598999ab0b2@mail.gmail.com>
Hi,
On Monday 13 February 2006 15:10, Khoa Nguyen wrote:
> > Have you tried it with more than one internal IP address connecting
> > to multiple destination addresses? Netfilter chooses the translated
> > source IP based on the source and destination address of the original
> > connection.
>
> Yes, if I tried with more than one internal IP address, the SNAT code
> would map to a different source IP address. This behaviour, however,
> is different from that of kernel 2.4.x ? I used to be able to simulate
> thousands of clients with SNAT and just one internal IP address. Is it
> possible to force the same round-robin behaviour in 2.6.12 kernel?
Unfortunately not, at least not without modifying the source code :) The
behaviour of the NAT code changed when Rusty's NAT simplifications were
merged in 2.6.11. I personally think this new behaviour is better than
the old one, as it provides increased performance and better cooperation
with load balancing solutions and other NAT-sensitive equipment.
Why exactly do you want to achieve the round-robin behaviour for one
internal IP?
--
KOVACS Krisztian
next prev parent reply other threads:[~2006-02-13 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 15:22 SNAT round-robin broken? Khoa Nguyen
2006-02-10 21:12 ` KOVACS Krisztian
[not found] ` <3d00e6dc0602130610j3ccc1c2cseaf06598999ab0b2@mail.gmail.com>
2006-02-13 20:45 ` KOVACS Krisztian [this message]
2006-02-13 21:01 ` Khoa Nguyen
2006-02-13 21:30 ` KOVACS Krisztian
2006-02-15 21:47 ` Khoa Nguyen
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=200602132145.27983@krak \
--to=hidden@sch.bme.hu \
--cc=khoa.coffee@gmail.com \
--cc=netfilter@lists.netfilter.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