All of lore.kernel.org
 help / color / mirror / Atom feed
From: KOVACS Krisztian <hidden@sch.bme.hu>
To: netfilter@lists.netfilter.org
Subject: Re: largescale NAT
Date: Tue, 27 Dec 2005 17:44:50 +0100	[thread overview]
Message-ID: <200512271744.51422@nienna> (raw)
In-Reply-To: <43B16A57.508@fiktiv.szgtikol.kando.hu>


  Hi,

On Tuesday 27 December 2005 17.22, DEXTER wrote:
> Why isn't there any documentation on how linux handles free, and
> occupied ports on a NAT box, how to fine tune the box when lots of user
> are behind it, etc..?
>
> So my question is: How to handle this situation? I mean, just 1 NAT
> linux box is able to handle all the 400+ users with the above
> situations? Or we have to do something like CONNLIMIT on source ips? Is
> there possibilities to balance the traffic on 2 or more NAT box?

  Whether or not your NAT box will be able to handle the situation mainly 
depends on your traffic pattern and available uplink bandwidth. For 400+ 
users the number of available ports on a single IP seems to be a serious 
limitation, so first of all you'd probably have to get multiple routable IP 
addresses and share connections between those multiple public IPs.

  The algorithm Netfilter uses to balance connections between multiple 
public IPs depends on the kernel version, so it's hard to say more about 
this without this crucial piece of information.

-- 
KOVACS Krisztian


  reply	other threads:[~2005-12-27 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-27 16:22 largescale NAT DEXTER
2005-12-27 16:44 ` KOVACS Krisztian [this message]
     [not found] ` <5d369d900512270859j45bc26f7i32397c1c6a6e12ea@mail.gmail.com>
2005-12-27 17:50   ` DEXTER
2005-12-27 18:45     ` Rob Sterenborg
2005-12-27 18:56       ` DEXTER
2005-12-28  0:03     ` Ishwar Rattan
2005-12-31 15:57 ` René Pfeiffer

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=200512271744.51422@nienna \
    --to=hidden@sch.bme.hu \
    --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 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.