All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Fugmann <afu@fugmann.dhs.org>
To: "Jens Lechtenbörger" <lechten@wi.uni-muenster.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: NEW vs INVALID
Date: Mon, 30 Sep 2002 16:39:07 +0200	[thread overview]
Message-ID: <3D98620B.2070707@fugmann.dhs.org> (raw)
In-Reply-To: m2elbb4w7h.fsf@pcwi1068.uni-muenster.de

Jens Lechtenbörger wrote:
> Hi there,
> 
> using stateful packet matching I wonder how an INVALID tcp packet is
> defined.  In particular, I set up a rule to log inbound NEW ssh
> connections to port 22:
> iptables -A INPUT  -m state --state NEW -p TCP --dport 22 -j LOG --log-level 5 --log-prefix "IPTABLES: Legal NEW TCP: "
> 
> What confuses me, is that this rule not only logs initial SYN
> packets but also (initial) packets with SYN and FIN set. 
> I thought that such packets should be INVALID...
SYN-FIN??? Are you sure of this? I would suspect some ACK-FIN when the 
connection closes, but not SYN-FIN.

Anyhow, AFAIK, the INVALID target only matches  ackets which are 
malformed. a SYN-FIN packets is not malformed as such. (But yes, SYN-FIN 
is an illegal combination, and should be dropped, though this is not the 
purpose of the INVALID match (IMHO, this can easily be done using 
standard netfilter rules).

Regards
Anders Fugmann

-- 
Neo: 'Can you fly that thing?'
Trinity: 'Not yet'.
$ apt-get install pilot-prg-v212helicopter.



  reply	other threads:[~2002-09-30 14:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 10:18 NEW vs INVALID Jens Lechtenbörger
2002-09-30 14:39 ` Anders Fugmann [this message]
2002-10-01  8:49   ` Cedric Blancher
2002-10-01  9:05     ` Anders Fugmann
2002-10-01 11:19       ` Cedric Blancher
2002-09-30 15:26 ` Cedric Blancher
2002-09-30 15:50   ` Jens Lechtenbörger
2002-10-01 10:33     ` Martijn Klingens

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=3D98620B.2070707@fugmann.dhs.org \
    --to=afu@fugmann.dhs.org \
    --cc=lechten@wi.uni-muenster.de \
    --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.