From: Jakov Sosic <jsosic@jsosic.homeunix.org>
To: netfilter@lists.netfilter.org
Subject: Re: why DROP in PREROUTING
Date: Fri, 27 Oct 2006 16:52:56 +0200 [thread overview]
Message-ID: <20061027165256.57d2e6d3@localhost> (raw)
In-Reply-To: <4541D89E.1080507@freemail.hu>
On Fri, 27 Oct 2006 11:59:58 +0200
Gáspár Lajos <swifty@freemail.hu> wrote:
> You can filter all of these packets at one point no matter where they
> coming from and going to....
Oscar is against it in his tutorial, he even says a reason. If I
remember correctly, it's beacuse only the first packet hits that rule,
and others get the same action without further checking, and that's not
a good idea to do.
--
| Jakov Sosic | ICQ: 28410271 | PGP: 0x244F89CA |
| http://jsosic.homeunix.org | jsosic@jsosic.homeunix.org |
--
prev parent reply other threads:[~2006-10-27 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 9:45 why DROP in PREROUTING Brent Clark
2006-10-27 9:59 ` Gáspár Lajos
2006-10-27 14:52 ` Jakov Sosic [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=20061027165256.57d2e6d3@localhost \
--to=jsosic@jsosic.homeunix.org \
--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