From: c0g <c0g@wp.pl>
To: netfilter-devel@lists.netfilter.org
Subject: "ip_conntrack_core: Frag of proto 17." error
Date: Thu, 18 Sep 2003 17:32:06 +0200 [thread overview]
Message-ID: <3F69CFF6.1060505@wp.pl> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
I'm getting lots of these errors. I read in ip_conntrack_core.c it
should "never happen" (so it's kind of assertion). Why does this
assertion fail?
I'm using 2.4.22 kernel with CVS p-o-m 20030907. I'm using only
following major netfilter patches:
TCPLAG.patch
ipt_REJECT-fake-source.patch
raw.patch
and some minor:
39_ip_conntrack-proc.patch
40_nf-log.patch
54_ip_nat-macro-args.patch
58-ip_conntrack-macro-args.patch
59_ip_nat_h-unused-var.patch
60_nat_tftp-remove-warning.patch
61-remove-memsets.patch
63_getorigdst-tuple-zero.patch
74_nat-range-fix.patch
ip_ct_refresh_optimization.patch
- --
c0g@wp.pl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/ac/2PqmVt5WhbA8RAm7oAJ9W+KUw6f4su9mpKUjMCbieracD+wCdHfut
3A++Y9/gobZCg/EwTCAlZhQ=
=zvIJ
-----END PGP SIGNATURE-----
next reply other threads:[~2003-09-18 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 15:32 c0g [this message]
2003-09-21 14:45 ` "ip_conntrack_core: Frag of proto 17." error Harald Welte
2003-09-22 9:26 ` c0g
2003-09-22 9:43 ` c0g
2003-09-22 10:03 ` 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=3F69CFF6.1060505@wp.pl \
--to=c0g@wp.pl \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.