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: Tue, 10 Oct 2006 07:04:50 +0200 [thread overview]
Message-ID: <452B29F2.70105@trash.net> (raw)
In-Reply-To: <00fb01c6e91d$08bf3570$4c01a8c0@elitecore26>
Nishit Shah wrote:
> Hi,
> During my load testing on kernel 2.6.16.13 i got following kernel
> oops. It occures when I enable SNAT or MASQUERADE for all outgoing traffic,
> with ACCEPT load testing works fine for me.
How exactly did you perform this testing? Did you loaded and unloaded
modules, or just loaded them? How many entries does the connection
tracking table have at the time?
next prev parent reply other threads:[~2006-10-10 5: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 [this message]
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
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=452B29F2.70105@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.