From: Patrick McHardy <kaber@trash.net>
To: webmaster@elnportal.it
Cc: Andrew Morton <akpm@osdl.org>,
netdev@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: Fw: [Bugme-new] [Bug 5936] New: Openswan tunnels + netfilter problem
Date: Sun, 22 Jan 2006 21:56:38 +0100 [thread overview]
Message-ID: <43D3F186.6030206@trash.net> (raw)
In-Reply-To: <20060122121301.033997ca.akpm@osdl.org>
Andrew Morton wrote:
>
> Begin forwarded message:
>
> Date: Sun, 22 Jan 2006 12:02:22 -0800
> From: bugme-daemon@bugzilla.kernel.org
> To: bugme-new@lists.osdl.org
> Subject: [Bugme-new] [Bug 5936] New: Openswan tunnels + netfilter problem
>
>
> http://bugzilla.kernel.org/show_bug.cgi?id=5936
>
> Summary: Openswan tunnels + netfilter problem
> Kernel Version: 2.6.16-rc1
> Status: NEW
> Severity: high
> Owner: laforge@gnumonks.org
> Submitter: webmaster@elnportal.it
>
>
> Jan 22 20:23:17 router kernel: Unable to handle kernel NULL pointer
> dereference at 000000000000009c RIP:
> Jan 22 20:23:17 router kernel: <ffffffff80345195>{xfrm4_output_finish+293}
> Jan 22 20:23:17 router kernel: PGD 35377067 PUD 0
> Jan 22 20:23:17 router kernel: Oops: 0000 [6]
> Jan 22 20:23:17 router kernel: CPU 0
> Jan 22 20:23:17 router kernel: Modules linked in: af_key deflate
> zlib_deflate twofish serpent blowfish sha256 crypto_null ae$
Please post your iptables rules and the full list of loaded modules.
next parent reply other threads:[~2006-01-22 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060122121301.033997ca.akpm@osdl.org>
2006-01-22 20:56 ` Patrick McHardy [this message]
2006-01-24 7:25 ` Fw: [Bugme-new] [Bug 5936] New: Openswan tunnels + netfilter problem Herbert Xu
2006-01-25 9:25 ` Patrick McHardy
2006-01-25 9:57 ` Herbert Xu
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=43D3F186.6030206@trash.net \
--to=kaber@trash.net \
--cc=akpm@osdl.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=webmaster@elnportal.it \
/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;
as well as URLs for NNTP newsgroup(s).