From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: difference between DROPped pings and non existing hosts
Date: Tue, 26 Apr 2005 17:12:21 -0500 [thread overview]
Message-ID: <426EBCC5.500@riverviewtech.net> (raw)
In-Reply-To: <426E8530.6080203@lopsch.com>
> I would like to know how ICMP distinguishes between DROPped pings and
> non existing hosts. Both times you don´t get a reply from the
> destination host but if it doesn´t reply because it doesn´t exist you
> get the correct destination unreachable message if it drops the requests
> for example with IPTables you get a timeout. And I haven´t a clue why
> this is so.
Just because you get an ICMP Host Unreachable message does not mean that the host is not there or that the router can not reach it. You should probably check the source IP on the ICMP message. I've had a discussion (with little feed back) on this list to this very effect. If the host that you are trying to reach wants to it can REJECT the packet with icmp-host-unreachable it can do so in lieu of DROPing the packet. In this situation you do see an ICMP Host Unreachable message, just from the IP address of the host in question that you are trying to reach, thus you know that someone is playing with you trying to make it so that you don't think the host in question is there.
Grant. . . .
prev parent reply other threads:[~2005-04-26 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 18:15 difference between DROPped pings and non existing hosts Daniel Lopes
2005-04-26 18:16 ` Tobias DiPasquale
2005-04-26 18:48 ` Daniel Lopes
2005-04-26 22:12 ` Taylor, Grant [this message]
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=426EBCC5.500@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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.