Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Jens Taprogge <jlt_lk@shamrock.dyndns.org>
To: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
	netfilter@lists.netfilter.org
Subject: 2.6.16-rc3 panic related to IP Forwarding and/or Netfilter
Date: Thu, 16 Feb 2006 01:10:56 +0100	[thread overview]
Message-ID: <20060216001056.GA7446@ranger.taprogge.wh> (raw)

Hello.

After upgrading from 2.6.13 an IP Masquerading router panics as soon as
soon as packages are forwarder (or rather should be).  As long as IP
Masquerading is disabled (and thus no forwarding occurs) the box runs
stable.

A picture of the panic ouput can be found at:
http://shamrock.dyndns.org/~ln/kernel/2.6.16rc3_panic/panic.jpg
The config is at:
http://shamrock.dyndns.org/~ln/kernel/2.6.16rc3_panic/config-2.6.16-rc3-g51d6aa16-dirty

The kernel was patched to support SIP-contrack however the extra files
have not been compiled and should thus have no influence.

Please cc me on replies as I am not subscribed to the lists.

Best Regards
Jens Taprogge

             reply	other threads:[~2006-02-16  0:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16  0:10 Jens Taprogge [this message]
2006-02-16  0:20 ` 2.6.16-rc3 panic related to IP Forwarding and/or Netfilter Patrick McHardy
2006-02-16 14:44   ` Jens Taprogge
2006-02-16 20:33     ` Patrick McHardy
2006-02-16 23:29       ` Jens Taprogge
2006-02-17  9:01       ` can't -j TARPIT angico
2006-02-17 12:50         ` Andre Ramoni
2006-02-17 21:18           ` angico
2006-02-20 13:46             ` Andre Ramoni
2006-02-20 19:25               ` angico
2006-02-20 19:38                 ` Andre Ramoni
2006-02-21 20:08                   ` angico
  -- strict thread matches above, loose matches on Subject: below --
2006-02-14 17:34 2.6.16-rc3 panic related to IP Forwarding and/or Netfilter Jens Taprogge
2006-02-15  6:52 ` 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=20060216001056.GA7446@ranger.taprogge.wh \
    --to=jlt_lk@shamrock.dyndns.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox