From: "Derick Anderson" <danderson@vikus.com>
To: bclark <bclark@eccotours.co.za>, netfilter@lists.netfilter.org
Subject: RE: icmp-host-unreachable as opposed to destination-unreachable
Date: Tue, 7 Mar 2006 10:23:15 -0500 [thread overview]
Message-ID: <FAC4E024BF776842876169173CE2F0132CBD29@mailbox.vikus.com> (raw)
> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org
> [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of bclark
> Sent: Tuesday, March 07, 2006 6:45 AM
> To: netfilter@lists.netfilter.org
> Subject: icmp-host-unreachable as opposed to destination-unreachable
>
> 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.
Derick Anderson
next reply other threads:[~2006-03-07 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 15:23 Derick Anderson [this message]
2006-03-07 16:33 ` icmp-host-unreachable as opposed to destination-unreachable Martijn Lievaart
-- 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=FAC4E024BF776842876169173CE2F0132CBD29@mailbox.vikus.com \
--to=danderson@vikus.com \
--cc=bclark@eccotours.co.za \
--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