All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lopes <lopsch@lopsch.com>
To: netfilter@lists.netfilter.org
Subject: Re: difference between DROPped pings and non existing hosts
Date: Tue, 26 Apr 2005 20:48:38 +0200	[thread overview]
Message-ID: <426E8D06.7050407@lopsch.com> (raw)
In-Reply-To: <876ef97a05042611161428df43@mail.gmail.com>

Tobias DiPasquale schrieb:
> On 4/26/05, Daniel Lopes <lopsch@lopsch.com> wrote:
> 
>>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.
> 
> 
> In the case where you get a destination unreachable message back, its
> the router that is responsible for the network on which the machine
> you are trying to ping that is responding with that message. When ICMP
> is dropped, the packet makes it to the host and thus the router does
> not generate a destination unreachable message to send back to you.
> 
Hmm I forgot the hardware address. In the case the router can´t do a 
address resolution he generates a ICMP error message because he won´t be 
able to deliver the packet is that right?
Thank´s so far for the reply :).


  reply	other threads:[~2005-04-26 18:48 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 [this message]
2005-04-26 22:12 ` Taylor, Grant

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=426E8D06.7050407@lopsch.com \
    --to=lopsch@lopsch.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.