Kernelpanic in 2.43
Subsystems (2)
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".
But this all works fine under 2.4.18 to 2.4.22. I haven't any idea, what that could be in 2.4.23.
If i should be more precise, please tell me what i should document.
Regards--
Ulrich
Quoted 7 lines · Ulrich Mensfeld
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.
Quoted 8 lines
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.
net/ipv4/netfilter/ip_fw_compat_masq.c +0 -3
@@ -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);
Signature · 1 line
/Martin