From: Cedric Blancher <blancher@cartel-securite.fr>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: netfilter mailing list <netfilter@lists.netfilter.org>
Subject: Re: are the four packet "states" all-encompassing?
Date: 24 Oct 2002 13:58:12 +0200 [thread overview]
Message-ID: <1035460692.18292.13.camel@elendil> (raw)
In-Reply-To: <Pine.LNX.4.44.0210240729250.31148-100000@localhost.localdomain>
Le jeu 24/10/2002 à 13:37, Robert P. J. Day a écrit :
> are the four conntrack states NEW, ESTABLISHED, RELATED and
> INVALID all-encompassing? that is, does every single packet
> fall into one and only one of these states?
Yes.
One very packet can have one state, and one.
> more to the point, what decides that a packet is NEW, given
> that it's possible for it to be categorized as NEW despite the
> fact that it has no SYN bit set? (i just noticed the part
> in the docs about identifying traffic that's NEW but also
> "-p tcp ! --syn".
A NEW packet is a valid packet that can't be associated to an existing
conntrack entry.
--
Cédric Blancher <blancher@cartel-securite.fr>
Consultant en sécurité des systèmes et réseaux - Cartel Sécurité
Tél: +33 (0)1 44 06 97 87 - Fax: +33 (0)1 44 06 97 99
PGP KeyID:157E98EE FingerPrint:FA62226DA9E72FA8AECAA240008B480E157E98EE
next prev parent reply other threads:[~2002-10-24 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 11:37 are the four packet "states" all-encompassing? Robert P. J. Day
2002-10-24 11:58 ` Cedric Blancher [this message]
2002-10-24 13:29 ` Robert P. J. Day
2002-10-24 13:57 ` Cedric Blancher
2002-10-24 13:58 ` Robert P. J. Day
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=1035460692.18292.13.camel@elendil \
--to=blancher@cartel-securite.fr \
--cc=netfilter@lists.netfilter.org \
--cc=rpjday@mindspring.com \
/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