From: noip <noip@webhost66.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel Panic when using iptables NAT rules with kernel 2.6.16.9
Date: Fri, 21 Apr 2006 13:31:39 +0000 [thread overview]
Message-ID: <20060421133139.32090.qmail@webhost66.com> (raw)
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.
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
Please send me a CC on reply because I'm not subscribed to the list.
Thank You
Iavor
next reply other threads:[~2006-04-21 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 13:31 noip [this message]
2006-04-21 22:01 ` Kernel Panic when using iptables NAT rules with kernel 2.6.16.9 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=20060421133139.32090.qmail@webhost66.com \
--to=noip@webhost66.com \
--cc=linux-kernel@vger.kernel.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