Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Subject: Re: Firewall Configuration Help
Date: Wed, 05 Aug 2009 15:35:55 +0200	[thread overview]
Message-ID: <4A798ABB.5000001@chello.at> (raw)
In-Reply-To: <47ae5fdc6d1c4a93d1035f61774996ec@localhost>

Julien Vehent wrote:
> Hello Nicholas,
>
>
> On Mon, 27 Jul 2009 13:56:59 -0400, NICHOLAS KLINE <nkline@kent.edu> wrote:
>   
>> # Tell netfilter that all TCP sessions do indeed begin with SYN
>>
>> $IPTABLES -A INPUT -p tcp ! --syn -m state --state NEW -j LOG
>> --log-prefix "Stealth scan attempt?"
>> $IPTABLES -A INPUT -p tcp ! --syn -m state --state NEW -j DROP
>>     
>
> My understanding of the conntrack subsystem is that a connection cannot be
> in the state NEW without a syn packet, therefore I don't think this is
> useful.
>
>
>   
Wrong, from the iptables tutorial 1.2.2 at frozentux:
http://iptables-tutorial.frozentux.net/iptables-tutorial.html#STATEMACHINE

The NEW state tells us that the packet is the first packet that we see. 
This means that the first packet that the conntrack module sees, within 
a specific connection, will be matched. For example, if we see a SYN 
packet and it is the first packet in a connection that we see, it will 
match. However, the packet may as well not be a SYN packet and still be 
considered NEW.

greets

Mart

  parent reply	other threads:[~2009-08-05 13:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 17:56 Firewall Configuration Help NICHOLAS KLINE
2009-07-28  9:09 ` Julien Vehent
2009-07-28 13:19   ` Billy Crook
2009-07-28 13:27     ` Julien Vehent
2009-07-28 22:08     ` /dev/rob0
2009-08-05 13:20   ` Mart Frauenlob
2009-08-05 13:51     ` Julien Vehent
2009-08-05 14:05       ` Mart Frauenlob
2009-08-05 13:35   ` Mart Frauenlob [this message]
2009-08-05 13:47     ` Julien Vehent
2009-08-05 18:21   ` Christoph A.
2009-08-05 12:56 ` 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=4A798ABB.5000001@chello.at \
    --to=mart.frauenlob@chello.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox