From: Alex Satrapa <alex@lintelsys.com.au>
To: netfilter@lists.netfilter.org
Subject: Re: could someone translate these rules inot plain english
Date: Fri, 23 Jan 2004 08:40:40 +1100 [thread overview]
Message-ID: <40104358.2050908@lintelsys.com.au> (raw)
In-Reply-To: <34137.66.65.52.125.1074768489.squirrel@sojourn.dyndns.org>
Technical wrote:
> If the default is that iptables to reject all packets that cannot not be
> deall with any of the previous rules, why would somemone use the last
> rule?? am I missing something??
It explicitly tells the remote computer that they're not *allowed* to
communicate with that host - as opposed to just dropping the packets
(pretending you're a black hole), or rejecting the packets with "host
unreachable" or "port unreachable". These two options imply that the
remote host is *allowed* to try connecting, but there's just nothing there.
The administrator at the other end would likely act different ways in
these circumstances. Upon noticing that there are many "host
unreachable" messages coming through, the administrator would take the,
"leave it alone and try again" stance - since the assumption would be
that something is broken. "host prohibited" messages explicitly state to
the administrator that everything is working just as it should be, and
that communication with that host is simply not allowed.
next prev parent reply other threads:[~2004-01-22 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 6:10 could someone translate these rules inot plain english Technical
2004-01-22 6:34 ` Ray Leach
2004-01-22 6:34 ` Alex Satrapa
2004-01-22 9:04 ` Arnt Karlsen
2004-01-22 10:48 ` Technical
2004-01-22 17:19 ` Unknown, Alistair Tonner
2004-01-22 19:04 ` Arnt Karlsen
2004-01-22 21:40 ` Alex Satrapa [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 16:18 bmcdowell
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=40104358.2050908@lintelsys.com.au \
--to=alex@lintelsys.com.au \
--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