From: Finite <wiretapped@gmail.com>
To: netfilter-devel@lists.netfilter.org
Subject: reproducible panic on 2.6.8.1
Date: Thu, 30 Sep 2004 01:15:06 -0700 [thread overview]
Message-ID: <bb51a00204093001151728a13@mail.gmail.com> (raw)
Greetings.
First let me say thank-you for netfilter; I have lost count of the
number of firewalls I've built with it. Excellent software!
Now onto the problem...
I just built linux 2.6.8.1 and am now having a very reproducible
kernel panic. After running my firewall script which should enable
simple masquerading from one interface to another, the machine will
panic as soon as it receives a packet which would be REJECTed. For
instance, under my current configuration, ICMP packets sent to the
router's IP from a machine on the LAN match the default REJECT policy,
and will trigger the panic every time. Also, under this kernel, the
masquerading doesn't work; packets are forwarded out to the net, but
the replies never make it back out to the LAN (ie maybe connection
tracking isn't working?). Even stranger, masquerading *did* work
momentarily when I first tried it (before the first panic) but hasn't
worked at all (under this kernel) since then. And if I flush the
tables, nothing I do will make it panic, but when I reload the rules
it will panic as soon as it tries to REJECT something.
Everything seems to work perfectly fine under my other kernel
(debian's "2.4.18-bf24").
I don't know how to get the full text of the kernel panic (how do I do
that btw?), but I copied down the end of it:
Code: 0f 0b 5f 5b 00 80 7f 44 c0 83 c4 14 5b c3 90 8d b4 26 00 00 00
Kernel panic: fatal exception in interrupt
In interrupt handler - not syncing
Thanks for any help!
reply other threads:[~2004-09-30 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bb51a00204093001151728a13@mail.gmail.com \
--to=wiretapped@gmail.com \
--cc=netfilter-devel@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.