From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Ulrich Mensfeld <koalasoft@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernelpanic in 2.43
Date: Tue, 09 Dec 2003 19:35:07 +0100 [thread overview]
Message-ID: <1070994906.813.18.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <8zZPc72uGbB@koalasoft>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
On Tue, 2003-12-09 at 01:00, Ulrich Mensfeld wrote:
> Hallo,
> don't know, whom to adress.
>
> I've following problem: Every Linux-Kernel above 2.4.22 crashes with
> capslock and scrolllock blinking, nothing in the message-log, and all i
> can do is magic-sysreq and boot.
>
> The problem seems to be reproducable: It seems to occur, when my son wants
> to use my pc as a router to the internet. So for detail:
>
> My pc acts as a dsl-router on "half"demand with packtfiltering and masq
> (ipchains) for 2 windows-pcs.
> "Half"demand means, my son has to make a "ping 10.0.0.2" to open an
> outgoing connection, to prevent a bunch of windows tools opening unwanted
> connections using "DoD".
This is a known bug :(
you have three choices:
1. Switch to iptables instead of ipchains.
2. Use 2.4.23-bk instead.
3. Apply the patch below.
--- linux.old/net/ipv4/netfilter/ip_fw_compat_masq.c 2002-11-29 05:22:53.000000000 +0530
+++ linux/net/ipv4/netfilter/ip_fw_compat_masq.c 2003-12-04 14:54:06.000000000 +0530
@@ -91,9 +91,6 @@
WRITE_UNLOCK(&ip_nat_lock);
return ret;
}
-
- place_in_hashes(ct, info);
- info->initialized = 1;
} else
DEBUGP("Masquerading already done on this conn.\n");
WRITE_UNLOCK(&ip_nat_lock);
--
/Martin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-12-09 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 0:00 Ulrich Mensfeld
2003-12-09 18:35 ` Martin Josefsson [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=1070994906.813.18.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=koalasoft@gmx.de \
--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
all inboxes | Powered by JetHome®