netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Salih Gönüllü" <sag@open.ch>
To: netfilter@vger.kernel.org
Subject: Global logging limit
Date: Fri, 19 Nov 2010 16:38:19 +0100	[thread overview]
Message-ID: <4CE699EB.1040100@open.ch> (raw)


Hi,

I am trying to enforce a global logging limit on my rule set. I would to 
like to be able to refer log entries to the causing rule too.

Here is what I am thinking of:


-N LogLimit
-A LogLimit -m limit --limit 3333/sec --limitburst 3000 -m MARK 
--set-mark  $LOGGING_MARK
-A LogLimit -j RETURN

....

-A ruleid:7906::: -p tcp -m tcp --dport 21 -j LogLimit
-A ruleid:7906::: -m MARK --mark $LOGGIN_MARK -j NFLOG --nflog-group 2 
--nflog-prefix "DROP by 7906"
-A ruleid:7906::: DROP

....

-A ruleid:7910::: -p tcp -m tcp --dport 389 -j LogLimit
-A ruleid:7910::: -m MARK --mark $LOGGIN_MARK -j NFLOG --nflog-group 2 
--nflog-prefix "DROP by 7910"
-A ruleid:7910::: DROP


Would I be paying a lot in term of performance by sending all dropped 
packets to the LogLimit chain ? I am using ulogd2, would it be better to 
put the limit in ulogd2 ?

Regards,

   -salih

                 reply	other threads:[~2010-11-19 15:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4CE699EB.1040100@open.ch \
    --to=sag@open.ch \
    --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).