Re: Ok to let all ICMP traffic through firewall?

From: Hairy One Kenobi (abuse_at_[127.0.0.1)
Date: 09/24/05


Date: Sat, 24 Sep 2005 13:07:04 GMT


"Leythos" <void@nowhere.lan> wrote in message
news:MPG.1d9d1560b23ca33698a0fe@news-server.columbus.rr.com...
> In article <KpHYe.4417$_56.2350@newsfe1-win.ntli.net>, abuse@[127.0.0.1]
> says...

<snip>

> > Undoubtedly the case. Although one could quote lots of instances where
it's
> > been damned useful.
> >
> > Well, *I* certainly can - usually when the web server has had a bit of a
> > funny turn, and one needs to tell if it's the server behind the firewall
> > (fat chance of fixing something from an adjacent continent), or whether
it's
> > the ISP playing silly buggers with the connection (marginally more hope
of
> > getting something sorted).
> >
> > As goes firewalls - I'm sure that most have already seen it, but:
> >
http://www.dilbert.com/comics/dilbert/archive/images/dilbert2813960050912.gif
>
> Funny, I don't expose our servers to Ping, and I seem to be able to
> monitor them all the time. If I need to expose PING to an external
> source I expose it to a specific IP and block all others.

I should have clarified (thought that it was clear from the context.. ah
well ;o)

This is monitorin my services from *outside* of the network.

Like most non-ISPs, I don't have a dedicated 24x7 staff to monitor systems
(this is a home network, before someone starts slinging companies that *do*
have this requirement).

On the Ping front, you'll find that the companies that you're hosting
(assuming that's what your part of the network does) are unlikely to appear
on many search engines - at least, that *used* to be the case - a "cheap"
PING before even attempting an HTTP GET.

Together, those made a pretty compelling case for me to switch ICMP back
on - I didn't (and still don't) see it as a major way threat to my firewall
(and, after all, that's as far as the packet's going to get, right?
Certainly not into the DMZ...)

H1K



Relevant Pages

  • Re: RDP can not logon error
    ... Tracert & Ping to dc on the same subnet as the server that is having trouble. ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: RDP can not logon error
    ... ping and tracert to the dc in that remote site (where this system ... Tracert & Ping to dc on the same subnet as the server that is having ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: RRAS Routing Problems
    ... erroneously routing through the DSL router. ... How to Setup Windows, Network, VPN & Remote Access on ... -All clients default routed to the RRAS Server ... 192.168.1.29: Cannot ping 192.168.2.29 ...
    (microsoft.public.windows.server.networking)
  • RE: VPN Resolution
    ... Microsoft CSS Online Newsgroup Support ... I currently am running a windows SBS2003 network and ... | cards, the member server has 1 nic, all nic's have static IP's. ... I can ping any address on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Ping failures.
    ... Laptop is Win XP Pro, Server is Windows Server 2003. ... the problem is that I get intermittent ping responses from the ... Now, If I plug the network cable back in, I SOMETIMES start to receive ...
    (microsoft.public.windows.server.networking)