All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: ѽ҉ᶬḳ℠ <vtol@gmx.net>
Cc: netfilter@vger.kernel.org
Subject: Re: [nftables] netdev rate limiting | timeouts rfq
Date: Mon, 28 Sep 2020 17:43:39 +0200	[thread overview]
Message-ID: <20200928154339.GA2605@salvia> (raw)
In-Reply-To: <c9a8646f-69b6-7333-b7ed-74f3d9747665@gmx.net>

On Mon, Sep 28, 2020 at 01:10:00PM +0000, ѽ҉ᶬḳ℠ wrote:
> On 28/09/2020 14:24, Pablo Neira Ayuso wrote:
> > On Mon, Sep 28, 2020 at 12:08:00PM +0000, ѽ҉ᶬḳ℠ wrote:
> > > In the below example it does not print any logs and since that stanza is
> > > right prior drop I reckon that since the log printing does not happen the
> > > frame dropping does neither.
> > > 
> > > table inet filter {
> > [...]
> > >          chain wan_pr {
> > >                  ct state { new } update @glv4 { ip saddr limit rate over
> > > 15/day burst 3 packets } log prefix "glv4 DROP: " flags all drop
> > >          }
> > > }
> > ct state new is restricting to match only on the first packet of the
> > connection.
> 
> Right, it should be then rather something with ct count, like:
> 
> ct state new update @glv4 { ip saddr ct count over 15 } log flags all prefix
> "glv4 DROP: " drop
> 
> but that produces:
> 
> Error: Could not process rule: Not supported

What would you like to achieve in first place?

This thread is starting to diverge from the original question.

  reply	other threads:[~2020-09-28 15:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 22:49 [nftables] netdev rate limiting | timeouts rfq ѽ҉ᶬḳ℠
2020-09-23  8:30 ` Pablo Neira Ayuso
2020-09-28 11:02   ` ѽ҉ᶬḳ℠
2020-09-28 11:52     ` Pablo Neira Ayuso
2020-09-28 12:08       ` ѽ҉ᶬḳ℠
2020-09-28 12:24         ` Pablo Neira Ayuso
2020-09-28 13:10           ` ѽ҉ᶬḳ℠
2020-09-28 15:43             ` Pablo Neira Ayuso [this message]
2020-09-28 16:03               ` ѽ҉ᶬḳ℠
2020-09-28 16:23                 ` Pablo Neira Ayuso
2020-09-28 16:47                   ` ѽ҉ᶬḳ℠
2020-09-28 17:01                     ` Pablo Neira Ayuso
2020-09-28 17:38                       ` ѽ҉ᶬḳ℠
2020-09-28 17:56                         ` Pablo Neira Ayuso
2020-09-28 18:15                           ` ѽ҉ᶬḳ℠
2020-09-28 19:19                             ` ѽ҉ᶬḳ℠

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=20200928154339.GA2605@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter@vger.kernel.org \
    --cc=vtol@gmx.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 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.