All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Matt Zagrabelny <mzagrabe@d.umn.edu>
Cc: netfilter <netfilter@vger.kernel.org>
Subject: Re: counter target
Date: Thu, 31 Aug 2023 17:32:11 +0200	[thread overview]
Message-ID: <ZPCye6qKuWeFAnCU@calendula> (raw)
In-Reply-To: <CAOLfK3UMF7V2izJfdTUMymiR=To8=icytybWXP8Md6fM1rOgDg@mail.gmail.com>

On Thu, Aug 31, 2023 at 10:25:15AM -0500, Matt Zagrabelny wrote:
> Hi Pablo,
> 
> On Sun, Aug 27, 2023 at 4:11 PM Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> >
> > On Fri, Aug 25, 2023 at 04:06:54PM -0500, Matt Zagrabelny wrote:
> > > Greetings netfilter,
> > >
> > > I have a question about the location of a "counter" statement.
> > >
> > > I see from the wiki [0] that placing a counter for the default policy
> > > comes *after* the policy:
> >
> > Wiki example does not refer to the default policy.
> 
> 
> Ahh. Now I see. Thanks for the clarification.
> 
> Is there a way to count the packets that get evaluated by the default
> policy of a chain?
> 
> I know I can put a counter after all my rules, but it seems like it
> would be nicer to somehow integrate it into:
> 
> chain IN {
>         type filter hook input priority filter; policy drop;
> 
> for example:
> 
> chain IN {
>         type filter hook input priority filter; policy counter drop;

Perhaps you mean something like this syntax:

         type filter hook input priority filter; counter; policy drop;

to enable basechain counters.

No, this is not supported.

> ...but the above fails.

You have to place a counter after all your rules to count those that
reach the basechain as you suggest.

  reply	other threads:[~2023-08-31 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 21:06 counter target Matt Zagrabelny
2023-08-27 21:11 ` Pablo Neira Ayuso
2023-08-31 15:25   ` Matt Zagrabelny
2023-08-31 15:32     ` Pablo Neira Ayuso [this message]
2023-08-31 15:49       ` Matt Zagrabelny

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=ZPCye6qKuWeFAnCU@calendula \
    --to=pablo@netfilter.org \
    --cc=mzagrabe@d.umn.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.