From: "René Pfeiffer" <lynx@luchs.at>
To: netfilter@lists.netfilter.org
Subject: Re: ICMP types to allow
Date: Thu, 22 Dec 2005 01:32:26 +0100 [thread overview]
Message-ID: <20051222003226.GJ25728@nightfall.luchs.at> (raw)
In-Reply-To: <1135202461.30754.38.camel@siren.chrisbrenton.org>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
On Dec 21, 2005 at 1701 -0500, Chris Brenton appeared and said:
> On Wed, 2005-12-21 at 20:22 +0100, Cedric Blancher wrote:
> >
> > In addition to this, Netfilter, unlike some popular proprietary
> > products, provide a proper stateful ICMP filtering. Just use it. Valid
> > ICMP errors will fall into RELATED state, others will be INVALID.
>
> Agreed. The payload on ICMP errors (which contains 28 bytes of the
> packet which generated the error) is inspected and compared against the
> state entry. This mean RELATED is more than capable of letting through
> needed ICMP errors and dropping the bogus stuff. So you are cool with
> types 3,4,5, & 11. The average perimeter does not need much more than
> that.
In addition to that you can add some general size limits for ICMP
packets. Theoretically ICMP packets can have 64 kB and there are tools
out there that use oversized packets for tunneling data.
Best,
René.
--
)\._.,--....,'``. Let GNU/Linux work for you while you take a nap.
/, _.. \ _\ (`._ ,. R. Pfeiffer <lynx at luchs.at> + http://web.luchs.at/
`._.-(,_..'--(,_..'`-.;.' - System administration + Consulting + Teaching -
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-22 0:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 13:45 ICMP types to allow Derick Anderson
2005-12-21 14:16 ` lst_hoe01
2005-12-21 16:27 ` Georgi Alexandrov
2005-12-21 19:22 ` Cedric Blancher
2005-12-21 22:01 ` Chris Brenton
2005-12-22 0:32 ` René Pfeiffer [this message]
2006-01-03 7:33 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2005-12-21 16:31 Peter E. Fry
2005-12-21 18:36 Derick Anderson
2005-12-21 18:48 ` John A. Sullivan III
2005-12-22 0:29 ` René Pfeiffer
2005-12-22 2:08 ` Chris Brenton
2005-12-22 11:03 ` René Pfeiffer
2005-12-22 8:50 ` lst_hoe01
2005-12-21 19:12 Derick Anderson
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=20051222003226.GJ25728@nightfall.luchs.at \
--to=lynx@luchs.at \
--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