From: "Jens Lechtenbörger" <lechten@wi.uni-muenster.de>
To: Cedric Blancher <blancher@cartel-securite.fr>
Cc: netfilter@lists.netfilter.org
Subject: Re: NEW vs INVALID
Date: 30 Sep 2002 17:50:31 +0200 [thread overview]
Message-ID: <m23crr4gu0.fsf@pcwi1068.uni-muenster.de> (raw)
In-Reply-To: <1033399610.1633.38.camel@elendil>
Cedric Blancher <blancher@cartel-securite.fr> writes:
> States a completly different concept than TCP connection, for it must
> also apply to UDP, or other layer 4 protocols, which can be
> connectionless.
>
> A NEW packet is a packet for which Netfilter cannot find an existing
> state in conntrack table. This packet, if TCP, can be SYN, as it should,
> but also ACK, or any flag combination you want. This packet, if allowed,
> create a state that will match following packets.
>
> An INVALID packet is a packet for which Netfilter cannot guess its
> state. Most of the time, it is ICMP errors that cannot be associated
> (i.e. RELATED) to an existing connection. You can also have ressources
> lack or bugs.
Thank you very much for this explanation!
> [...]
>
> To be strict, your iptables command should be :
>
> iptables -A INPUT -m state --state NEW -p TCP --dport 22 --syn -j LOG --log-level 5 --log-prefix "IPTABLES: Legal NEW TCP: "
>
In fact, I had a similar command, but this again allows
SYN+FIN-packets.
What I am doing now is
"--state NEW --tcp-flags SYN,ACK,FIN,RST SYN"...
I was just wondering about the meaning of INVALID, which you
explained above.
Thanks again,
Jens
next prev parent reply other threads:[~2002-09-30 15:50 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
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 [this message]
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=m23crr4gu0.fsf@pcwi1068.uni-muenster.de \
--to=lechten@wi.uni-muenster.de \
--cc=blancher@cartel-securite.fr \
--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