From: Sander Smeenk <ssmeenk+netfilter@freshdot.net>
To: netfilter@lists.netfilter.org
Subject: Kernel >= 2.6.5, ip_conntrack and udp traffic
Date: Thu, 12 Aug 2004 09:56:07 +0200 [thread overview]
Message-ID: <20040812075607.GA7616@freshdot.net> (raw)
Hello,
I am one of the few people experiencing problems with UDP traffic being
connection tracked and somehow causing the iptables code to start
blurting out:
Aug 5 12:56:48 valor kernel: ip_conntrack_in: Frag of proto 17 (hook=0)
Aug 5 12:56:48 valor kernel: NF_IP_ASSERT:
net/ipv4/netfilter/ip_nat_standalone.c:83(ip_nat_fn)
Aug 5 12:56:48 valor kernel: ip_conntrack_in: Frag of proto 17 (hook=0)
When I try to access my sfs mounts. Google shows this has to do with a
NFS mount to localhost, with r/wsize set to >8192 bytes.
Is sfs/nfs behaving badly, or is the iptables core?
Previously, with kernels < 2.6.8-rcN, I could 'work around' this problem
by not-tracking UDP traffic, but this doesn't seem to work anymore with
the newest kernels...
There's not a lot of information in google about this problem. Am I one
of the few that experience this?
Kind regards,
Sander.
--
| Where are the first 6-up's ?
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D
reply other threads:[~2004-08-12 7:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040812075607.GA7616@freshdot.net \
--to=ssmeenk+netfilter@freshdot.net \
--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