From: seberino@spawar.navy.mil
To: Lopsch <lopsch@lopsch.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: valid INPUT/OUTPUT rule piece?--> '-p tcp --tcp-flags ACK, FIN FIN -j DROP', etc.
Date: Tue, 25 Jan 2005 21:26:58 -0800 [thread overview]
Message-ID: <20050126052658.GA17112@spawar.navy.mil> (raw)
In-Reply-To: <41F6E665.6010000@lopsch.com>
Lopsch
Thanks for your email. I know a little about TCP flags.
IIRC, ACK means 'Acknowlegement'
and FIN means 'Finish Connection'.
Why would TCP want everyone to turn on ACK when they
want to finish a connection with FIN?
I assume that TCP was written to do 2 errands in one
TCP datagram?...1. acknowledge last datagram received
2. terminate connection
It seems odd you can't terminate a connection (FIN)
without also acknowledging something to me.
Chris
On Wed, Jan 26, 2005 at 01:37:57AM +0100, Lopsch wrote:
> seberino@spawar.navy.mil schrieb:
> >Please explain these:
> >
> >$IPTABLES -t filter -A INPUT -p tcp --tcp-flags ACK,FIN FIN -j DROP
> >$IPTABLES -t filter -A INPUT -p tcp --tcp-flags ACK,PSH PSH -j DROP
> >$IPTABLES -t filter -A INPUT -p tcp --tcp-flags ACK,URG URG -j DROP
> >$IPTABLES -t filter -A INPUT -p tcp --tcp-flags ALL NONE -j DROP
> >
> >Do first 3 imply you must send ACK when you send a FIN, PSH or URG?
> >
> >And does last mean you must set *some* TCP flag always?
> >
> >CS
> >
> >
> Exactly. The first 3 rules are used for dropping packets which have set
> FIN, PSH and URG but without a set ACK-flag. The last one prevents empty
> packets (none flag set) to enter your network.
> As often such packets are used by portscans it is useful to drop them.
> Jason posted a link some time ago with a list of rules to perform tcp
> checks http://www.stearns.org/modwall/sample/tcpchk-sample
>
> --
>
> PGP-ID 0xF8EAF138
--
_______________________________________
Christian Seberino, Ph.D.
SPAWAR Systems Center San Diego
Code 2872
49258 Mills Street, Room 158
San Diego, CA 92152-5385
U.S.A.
Phone: (619) 553-9973
Fax : (619) 553-6521
Email: seberino@spawar.navy.mil
_______________________________________
next prev parent reply other threads:[~2005-01-26 5:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 0:18 valid INPUT/OUTPUT rule piece?--> '-p tcp --tcp-flags ACK, FIN FIN -j DROP', etc seberino
2005-01-26 0:37 ` Lopsch
2005-01-26 5:26 ` seberino [this message]
2005-01-26 19:08 ` Jason Opperisano
2005-01-26 19:40 ` seberino
2005-01-31 20:42 ` seberino
2005-01-31 21:04 ` Jason Opperisano
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=20050126052658.GA17112@spawar.navy.mil \
--to=seberino@spawar.navy.mil \
--cc=lopsch@lopsch.com \
--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