From: "Klemen Kecman" <klemen@sting.si>
To: netfilter@lists.netfilter.org
Subject: Re: Logging with INPUT & FORWARD set to DROP
Date: Tue, 9 Mar 2004 12:08:51 +0100 [thread overview]
Message-ID: <002b01c405c6$e81d6300$6a02a8c0@klemen> (raw)
In-Reply-To: 200403091059.54342.Antony@Soft-Solutions.co.uk
Thanks! ;)
----- Original Message -----
From: "Antony Stone" <Antony@Soft-Solutions.co.uk>
To: <netfilter@lists.netfilter.org>
Sent: Tuesday, March 09, 2004 11:59 AM
Subject: Re: Logging with INPUT & FORWARD set to DROP
> On Tuesday 09 March 2004 10:48 am, Klemen Kecman wrote:
>
> > Is there a way to log packets that get dropped due to default policy set
to
> > drop.
>
> Sure. Place a LOG rule at the end of the chain in question.
>
> Antony.
>
> --
> If the human brain were so simple that we could understand it,
> we'd be so simple that we couldn't.
>
> Please reply to the
list;
> please don't CC
me.
>
>
prev parent reply other threads:[~2004-03-09 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 10:48 Logging with INPUT & FORWARD set to DROP Klemen Kecman
2004-03-09 10:59 ` Antony Stone
2004-03-09 11:08 ` Klemen Kecman [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='002b01c405c6$e81d6300$6a02a8c0@klemen' \
--to=klemen@sting.si \
--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