From: Patrick McHardy <kaber@trash.net>
To: noip <noip@webhost66.com>
Cc: linux-kernel@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: Kernel Panic when using iptables NAT rules with kernel 2.6.16.9
Date: Sat, 22 Apr 2006 00:01:34 +0200 [thread overview]
Message-ID: <4449563E.9000504@trash.net> (raw)
In-Reply-To: <20060421133139.32090.qmail@webhost66.com>
noip wrote:
> Hello,
>
> After the upgrade to kernel 2.6.16.9 i'm receiving a kernel panic almost immediately when I enter my iptables REDIRECT rules. If I don't enter these rules, the machine works fine.
> I've observed this behavior on all of my machines that are running Broadcom Gbit Ethernet cards using tg3 driver.
> On my office machine with the same kernel and the same iptables rules there is no such problem - I have an Intel 10/100 Ethernet card.
> My kernel is patched with the Grsecurity patch and with the connlimit patch.
> I've tried the same setup without Gresecurity but the problem was still there.
Which kernel version did you run before that?
> My iptables version is 1.3.5.
>
> My kernel config - http://server260.com/panic/kerncfg
> A screenshot with the panic - http://server260.com/panic/panic.gif
The interesting part scrolled off the screen, please set
CONFIG_STACK_BACKTRACE_COLS=2 and try again. The last thing I
can see is ipt_do_table, if you are using connlimit in LOCAL_IN
its most likely that, the version in patch-o-matic is not
compatible with current kernels.
prev parent reply other threads:[~2006-04-21 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 13:31 Kernel Panic when using iptables NAT rules with kernel 2.6.16.9 noip
2006-04-21 22:01 ` 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=4449563E.9000504@trash.net \
--to=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=noip@webhost66.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.