Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Martijn Lievaart" <m@rtij.nl>
To: danderson@vikus.com
Cc: netfilter@lists.netfilter.org
Subject: RE: icmp-host-unreachable as opposed to destination-unreachable
Date: Tue, 7 Mar 2006 17:33:48 +0100 (CET)	[thread overview]
Message-ID: <13274.217.166.60.19.1141749228.squirrel@ma.rtij.nl> (raw)
In-Reply-To: <FAC4E024BF776842876169173CE2F0132CBD29@mailbox.vikus.com>

Derick Anderson zei:
>
>
> bclark said:

>> Hi all
>>
>> Would anyone be kind to explain why would a person reject a
>> connection to port 113 with icmp-host-unreachable as opposed
>> to destination-unreachable.
>> I probally dont understand the difference.
>> Just something I was wondering.
>>
>> Kind Regards
>> Brent Clark
>>
>
>>From what I can tell, icmp-host-unreachable is a code (1) for the
> destination-unreachable ICMP type (3). See
> http://www.spirit.com/Resources/icmp.html for a little more information,
> and Google RFC 792 for a lot more information.
>
> Basically though, "host-unreachable" is more specific than
> "destination-unreachable". I would think that code 3 would be more
> appropriate ("port unreachable") to this specific rule but then I don't
> bother with ident (port 113) rules. There's more information on that on
> this page: http://grc.com/port_113.htm.

Actually one should respond with a tcp reset to tcp/113. All icmp
*-unreachable replies can (and do) give differing results on different
sending tcp stacks.

HTH,
M4




  reply	other threads:[~2006-03-07 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 15:23 icmp-host-unreachable as opposed to destination-unreachable Derick Anderson
2006-03-07 16:33 ` Martijn Lievaart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-07 11:44 bclark

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=13274.217.166.60.19.1141749228.squirrel@ma.rtij.nl \
    --to=m@rtij.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox