All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter E. Fry" <pfry@redsword.com>
To: Derick Anderson <danderson@vikus.com>, netfilter@lists.netfilter.org
Subject: Re: ICMP types to allow
Date: Wed, 21 Dec 2005 10:31:52 -0600	[thread overview]
Message-ID: <43a98378.243.910.4543@redsword.com> (raw)


----- Original Message -----
From: "Derick Anderson" <danderson@vikus.com>
To: <netfilter@lists.netfilter.org>
Subject: ICMP types to allow
Date: Wed, 21 Dec 2005 08:45:04 -0500

> I know that some networks just drop all ICMP to prevent
> traceroutes but recently I've been been seeing problems
> related to fragementation and MTU and wondering if
> dropping ICMP is causing some of that (since
> Fragementation Needed packets can't get through). On the
> flip side of that there's the Source Quench and
> Fragmentation Needed DoS attacks which have recently
> become mildly popular (I've gotten a few hits on Snort but
> not that many). 
> 
> I'd like to hear from the list what ICMP types firewall
> admins are allowing and why - what are the risks for
> allowing certain types vs. the risks of NOT allowing them?

  In Cisco terms, I always allow
"administratively-prohibited", "echo", "echo-reply",
"packet-too-big", "time-exceeded", "unreachable" (I'm too
lazy to pull out the actual types), with appropriate shaping
and rate-limits to avoid killing the small upstream on my
DSL and/or becoming a 1:1 reflector of any significance.  In
ten years (five with ISDN), I've never actually been
seriously attacked through ICMP -- if someone's going to
flood you, they'll flood you, and it'd take one lazy bastage
not to adapt to whatever filters you have in place.  The
most trash I've seen has not been ICMP, but UDP from berserk
M$ virii (in part because I'm a 'Net-nobody and I haven't
gotten the urge lately to hop on IRC and call all of the
2600 types a bunch of wusses who can't touch my mighty DSL).
 Me, I like ICMP -- I find it useful with little
risk/impact.  Your mileage may vary.

Peter E. Fry



             reply	other threads:[~2005-12-21 16:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 16:31 Peter E. Fry [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-21 19:12 ICMP types to allow Derick Anderson
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 13:45 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
2006-01-03  7:33 ` Jan Engelhardt

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=43a98378.243.910.4543@redsword.com \
    --to=pfry@redsword.com \
    --cc=danderson@vikus.com \
    --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.