All of lore.kernel.org
 help / color / mirror / Atom feed
From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Allowing ping
Date: Wed, 26 Oct 2005 10:55:48 -0500	[thread overview]
Message-ID: <200510261055.48199.rob0@gmx.co.uk> (raw)
In-Reply-To: <435E6C3A.20709@beaconet.net>

On Tuesday 2005-October-25 12:32, Askar Ali wrote:
> I have a very simple question, presently we are blocking icmp
> "ping" on our servers. But as far I can userderstand its not very
> good practice or providing a good security by blocking ping request.

I agree. Blocking pings is like shooting yourself in the foot.  You 
never know when you will need ping. Some think it's a good idea to try 
to hide. Rubbish, if you have any open services, the bots and worms 
will find you anyway.

> see one can ping www.xyz.com and get the reply back.
>
> However Before allowing ping "echo-request" I just want to confirm
> whether doing ...
>
> iptables -A INPUT -p icmp --icmp-type echo-request -j ACCEPT
>
> would be enough or doing some rate limiting would be better?

I think a reasonable --limit is not a bad idea, but there is no 
objective measurement of "better". I use a --limit on incoming ping 
requests. It might help in the event of a flood ping attack, and you 
can still ping to verify your connectivity when you need it.
-- 
    mail to this address is discarded unless "/dev/rob0"
    or "not-spam" is in Subject: header


  reply	other threads:[~2005-10-26 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 17:32 Allowing ping Askar Ali
2005-10-26 15:55 ` /dev/rob0 [this message]
2005-10-26 15:59   ` Pablo Sanchez
2005-10-26 16:24   ` Askar

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=200510261055.48199.rob0@gmx.co.uk \
    --to=rob0@gmx.co.uk \
    --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.