From: Peter Grace <pgrace@rttx.com>
To: linux-kernel@vger.kernel.org
Subject: POSSIBLE BUG: netfilter/ip_conntrack_core
Date: Mon, 16 Feb 2004 09:59:41 -0500 [thread overview]
Message-ID: <4030DADD.1040104@rttx.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
~ I'm posting to the list blindly this following report:
LIST_DELETE: net/ipv4/netfilter/ip_conntrack_core.c:295
&ct->tuplehash[IP_CT_DIR_REPLY] (c40bf384) not in &ip_conntrack_hash[hr]
I believe the memory addresses are not as pertinent as the message
itself, but the screen filled up with 4-5 of these lines before finally
biting the dust.
Can someone shoot me an e-mail in reply to let me know if this is a bug
in netfilter code or if I'm just somehow confusing the heck out of the
nat filter? I've got a set of nat forwarding rules that forwards an ip
address onto the internal lan, and then from there I'm only allowing
certain packets to go through -- that seems to have exacerbated the
problem..
Thanks in advance!
Pete
- --
- ---
/------------------------------------------------\
|Peter Grace Phone: 484-875-9462
|Technology Analyst Fax: 484-875-9461
|RealTime Technologies, Inc. Cell: 484-919-1400
|835 Springdale Drive, Suite 101
|Exton, PA 19341
\------------------------------------------------/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAMNrc1bytwQSw7hoRAlAdAKDRNDHBduc9hohuYZDiq05u3HFsLACgzFUA
Vkee3U/KD1+wrWRWBohbWCM=
=j2ZU
-----END PGP SIGNATURE-----
next reply other threads:[~2004-02-16 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 14:59 Peter Grace [this message]
2004-02-17 14:04 ` POSSIBLE BUG: netfilter/ip_conntrack_core Harald Welte
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=4030DADD.1040104@rttx.com \
--to=pgrace@rttx.com \
--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