From: "Roman Ledovskiy" <roman@usonyx.net>
To: netfilter@vger.kernel.org
Subject: conntrack INVALID packets
Date: Wed, 31 Oct 2007 23:14:35 +0800 [thread overview]
Message-ID: <000401c81bd0$c0080e00$40182a00$@net> (raw)
Hi,
I have linux firewall in between internet and my network, diagram is
following:
Upstream
|
Firewall server
|
my network
"My network" hosts many different email/web servers.
Firewall server is not a bridge, it has 2 interfaces (one to upstream, one
to internal network)
Not much kernel configuration, kernel is default kernel from Centos5 x64
repo: 2.6.18-8.1.10.el5
On this server I get quite a lot of INVALID packets, about 0.07% of all and
I can't figure out why..
Iptables output is quite big so can't post it here, but the logic is simple
- inspect NEW packets, accept RELATED/ESTABLISHED, drop INVALID.
Conntrack is not full:
net.ipv4.netfilter.ip_conntrack_count = 5888
net.ipv4.netfilter.ip_conntrack_max = 65536
server has a lot of free memory also.
It is not ip_conntrack_tcp_be_liberal or ip_conntrack_checksum (changing
these values doesn't help)
There is definitely something wrong because I see INVALID packets not only
from outside -> my network, but from my network -> reverse also (although a
lot less)
The only thing I can think of is that one of "ip_conntrack_*_timeout*"
values is reached and conntrack removes connection (and after that there is
one more packet in regards to that deleted connection)
Could anybody tell possible reasons for packet being marked as INVALID
besides those mentioned above.
Any help is appreciated.
Thanks
Roman Ledovskiy
next reply other threads:[~2007-10-31 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 15:14 Roman Ledovskiy [this message]
2007-11-08 7:47 ` conntrack INVALID packets Olivier Sessink
-- strict thread matches above, loose matches on Subject: below --
2009-06-02 16:19 Xesc Arbona
2009-06-03 7:23 ` Jozsef Kadlecsik
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='000401c81bd0$c0080e00$40182a00$@net' \
--to=roman@usonyx.net \
--cc=netfilter@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 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.