From: Christoph Paasch <christoph.paasch@gmail.com>
To: Gilad Benjamini <gilad.benjamini@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: INVALID state
Date: Fri, 14 Nov 2008 00:01:30 +0100 [thread overview]
Message-ID: <200811140001.31179.christoph.paasch@gmail.com> (raw)
In-Reply-To: <491cab7d.27b38c0a.772a.42ee@mx.google.com>
On Thu November 13 2008, Gilad Benjamini wrote:
> Back to my original question then: what is the rule of thumb ?
> In other words, for a non-programmer reading proper documentation, how
> would the documentation describe INVALID ?
In the "Packet Filtering HOWTO" of netfilter.org, they say:
A packet which could not be identified for some reason: this includes running
out of memoory and ICMP errors which don't correspond to any known connection.
By looking to the code, I would say, that a packet is invalid, if the
connection tracker doesn't manages to create a proper connection-state for
that packet (memory-errors while treating the packet, ...), or the tests
defined by the specific protocol-handlers fail.
But I'm also asking me this question, because I have to implement shim6-
support in netfilter in the case of my Master Thesis. So does somebody can give
me a reference which will explain me, what a firewall should check, and what
not...? Should it check, if the packet respects the whole protocol (in case of
shim6: nonces, cga/hba, ...)?
Thanks for your help, and sorry, if i'm running out of the topic of that
thread.
--
Christoph Paasch
www.rollerbulls.be
--
next prev parent reply other threads:[~2008-11-13 23:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 18:16 INVALID state Gilad Benjamini
2008-11-13 22:31 ` Christoph Paasch
2008-11-13 22:34 ` Gilad Benjamini
2008-11-13 23:01 ` Christoph Paasch [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-28 9:24 Nemeth Denes
2010-02-28 10:10 ` Mart Frauenlob
2010-02-28 10:52 ` Nemeth Denes
2010-02-28 11:15 ` Mart Frauenlob
2008-11-12 22:08 Gilad Benjamini
2008-11-13 11:13 ` Thomas Jacob
2008-11-13 12:16 ` Christoph Paasch
2008-11-13 12:48 ` Thomas Jacob
2008-11-13 13:08 ` Christoph Paasch
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=200811140001.31179.christoph.paasch@gmail.com \
--to=christoph.paasch@gmail.com \
--cc=gilad.benjamini@gmail.com \
--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