From: "Bob Sauvage" <Bob.sauvage@gmx.fr>
To: netfilter@vger.kernel.org
Subject: Some packets flagged INVALID
Date: Tue, 18 Feb 2014 22:52:18 +0100 [thread overview]
Message-ID: <20140218215218.194660@gmx.com> (raw)
Hi *,
I'm running a high volume web application that uses Apache 2.2.15 mod_proxy to reverse proxy content from apache to JBoss 6.
I found 503 errors which happen sporadically throughout the day on random requests (perhaps 1/1000 of daily requests).
After investigations, I noticed that every error coincides with an invalid tcp packet:
kernel: invalid:IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=33082 DF PROTO=TCP SPT=48340 DPT=8080 WINDOW=32792 RES=0x00 SYN URGP=0
After some investigations, this SYN packet is not acknowledged by JBoss in order to perform the TCP 3-Way Handshake. Mhmm, strange, I decide to investigate in firewall rules, build by another sysadmin:
In the INPUT chain, I found a rule that logs and REJECTS all INVALID packets:
iptables -A INPUT -m state --state INVALID -j LOG --log-prefix "invalid:"
iptables -A INPUT -m state --state INVALID -j REJECT
Then logs and REJECTS not SYN but new:
iptables -A INPUT -p tcp ! --syn -m state --state NEW -j LOG --log-prefix "new-not-syn:"
iptables -A INPUT -p tcp ! --syn -m state --state NEW -j REJECT --reject-with tcp-reset
I decided to add a rule in order to ACCEPT all packets from 127.0.0.1 to or from port 8080.
Since this update, I don't see this kind of errors anymore.
Why does iptables tag this packet as invalid ?
Thanks,
Bob
next reply other threads:[~2014-02-18 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 21:52 Bob Sauvage [this message]
2014-02-18 22:26 ` Some packets flagged INVALID Neal Murphy
2014-02-18 22:38 ` Mart Frauenlob
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=20140218215218.194660@gmx.com \
--to=bob.sauvage@gmx.fr \
--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.