All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Nishit Shah <nishit@elitecore.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: kernel oops with NAT in 2.6.16.13 kernel
Date: Wed, 11 Oct 2006 09:04:06 +0200	[thread overview]
Message-ID: <452C9766.4020304@trash.net> (raw)
In-Reply-To: <002f01c6ed00$c21c5f20$4c01a8c0@elitecore26>

Nishit Shah wrote:
> Are you talking about MASQ/SNAT case  ??

Yes.

> well in both NAT cases upto 4000 c/s, everything is pretty same, but at
> 3,00,000 connections, system is freezed in MASQ/SNAT case, so don't have
> idea about c/s rate degradation.

Try SNATing to multiple IPs using multiple rules and some match to
distribute the traffic (like matching on even/uneven IPs or something
like that). That should show if finding a unique tuple really is the
problem.

      reply	other threads:[~2006-10-11  7:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06  7:57 kernel oops with NAT in 2.6.16.13 kernel Nishit Shah
2006-10-10  5:04 ` Patrick McHardy
2006-10-10  5:50   ` Nishit Shah
2006-10-10  6:01     ` Patrick McHardy
2006-10-10  6:28       ` Nishit Shah
2006-10-11  5:52         ` Patrick McHardy
2006-10-11  6:44           ` Nishit Shah
2006-10-11  7:04             ` 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=452C9766.4020304@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=nishit@elitecore.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.