From: Joel Newkirk <firewalldude@newkirk.us>
To: tedkaz@optonline.net
Cc: netfilter@lists.netfilter.org
Subject: Re: Chain Policy DROP versus ACCEPT and logging
Date: Sun, 12 Oct 2003 11:06:11 -0400 [thread overview]
Message-ID: <1065971170.2922.104.camel@alpha.newkirk.us> (raw)
In-Reply-To: <1065967220.5801.10.camel@tarkus>
On Sun, 2003-10-12 at 10:00, Ted Kaczmarek wrote:
> I have seen many setups where the default CHAIN Policy is to accept
> packets by default versus dropping them.
> >From my perspective a firewall should implicitly deny everything, hence
> INPUT and FORWARD should be DROP.
> Then rules are put in to allow what you want.
> But, one seems to lose some logging capabilities with such a setup.
> Is their a way to log the default INPUT and FORWARD policies for dropped
> packets with them set to DROP as opposed to having them set to ACCEPT
> and putting in logs for any deny rules.
Yep, just make a log rule last in the chain...
iptables -A FORWARD -j LOG --log-level 7 --log-prefix "FWDDROP:"
for instance. Just remember that any rules added after this cannot
simply be "-A", or they'll be appended after the log rule. They'll
still work properly but the packets they accept would be logged as
having been dropped.
j
next prev parent reply other threads:[~2003-10-12 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 14:00 Chain Policy DROP versus ACCEPT and logging Ted Kaczmarek
2003-10-12 15:06 ` Joel Newkirk [this message]
2003-10-12 15:12 ` Cedric Blancher
-- strict thread matches above, loose matches on Subject: below --
2003-10-13 15:54 bmcdowell
2003-10-14 1:01 ` Ted Kaczmarek
2003-10-14 1:29 ` Jeffrey Laramie
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=1065971170.2922.104.camel@alpha.newkirk.us \
--to=firewalldude@newkirk.us \
--cc=netfilter@lists.netfilter.org \
--cc=tedkaz@optonline.net \
/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