From: David ROBERT <castlebbs@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: Log and Drop with OSSEC
Date: Thu, 13 May 2010 10:47:46 +0100 [thread overview]
Message-ID: <AANLkTimTmGE4buHzSZCgNy5XEEhR5_h0jeJf-i9CTr85@mail.gmail.com> (raw)
In-Reply-To: <m2x57bfe46c1005070841of1b6cdc7paaef031f3995679b@mail.gmail.com>
Hi All,
This was too obvious so I couldn't find it... I did a "-I" for the
DROP rule, so obviously it was matched before the LOG rule... tsss..
David
2010/5/7 David ROBERT <castlebbs@gmail.com>:
> Hi All,
>
> I have a very basic question. I am updating an active response script
> for OSSEC that add DROP rules. I added rules to log packets being
> dropped:
> Ex for IP 1.1.1.1
>
> iptables -I INPUT -s 1.1.1.1 -m limit --limit 1/sec -j LOG
> --log-prefix OSSEC-HIDS --log-level 7 (rule added)
> iptables -I INPUT -s 1.1.1.1 -j DROP (original rule)
>
> It doesn't log, it actually logs if I only run the first rule, as soon
> as I run the DROP rule, it DROP packets indeed, but it won't log
> anymore.
--
David ROBERT
prev parent reply other threads:[~2010-05-13 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 15:41 Log and Drop with OSSEC David ROBERT
2010-05-13 9:47 ` David ROBERT [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=AANLkTimTmGE4buHzSZCgNy5XEEhR5_h0jeJf-i9CTr85@mail.gmail.com \
--to=castlebbs@gmail.com \
--cc=david@ombrepixel.com \
--cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).