From: Kevin Van Workum <vanw@usna.edu>
To: netfilter@lists.netfilter.org
Subject: bad tcp packets?
Date: Mon, 31 Jan 2005 08:29:56 -0500 [thread overview]
Message-ID: <41FE32D4.4000103@usna.edu> (raw)
I'm learning about iptables and am working through the example scripts
in Oskar Andreasson's Iptables Tutorial 1.1.19. So I have the following
rules:
iptables -A bad_tcp_packets -p tcp ! --syn -m state --state NEW -j LOG
--log-prefix "New not syn:"
iptables -A bad_tcp_packets -p tcp ! --syn -m state --state NEW -j DROP
My understanding of this rule is that all NEW tcp packets should by SYN
also. So if they are not NEW and SYN, then we should log them and drop
them. I guess Andreasson wants to log them because they may indicate a
problem of some sort. So in my log file, I get this:
Jan 30 20:09:27 server kernel: New not syn:IN= OUT=lo SRC=10.0.0.100
DST=10.0.0.100 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=7678 DF PROTO=TCP
SPT=34928 DPT=143 WINDOW=32767 RES=0x00 ACK PSH FIN URGP=0
So what's the problem with these packets? It looks like some client is
contacting the imapd (which is running on my firewall) with some bad tcp
packets?
--
Kevin
next reply other threads:[~2005-01-31 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 13:29 Kevin Van Workum [this message]
2005-01-31 18:34 ` bad tcp packets? Jose Maria Lopez
2005-02-01 12:33 ` Kevin Van Workum
2005-02-01 16:28 ` Jose Maria Lopez
2005-02-02 7:56 ` 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=41FE32D4.4000103@usna.edu \
--to=vanw@usna.edu \
--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 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.