From: Florian Westphal <fw@strlen.de>
To: ѽ҉ᶬḳ℠ <vtol@gmx.net>
Cc: darius <dram@mailbox.org>,
"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Metering is not working with dynamic sets on nft v0.9.2
Date: Fri, 7 Feb 2020 11:17:40 +0100 [thread overview]
Message-ID: <20200207101740.GC6466@breakpoint.cc> (raw)
In-Reply-To: <4d26b387-5466-d57d-6191-dcbe8926ec01@gmx.net>
ѽ҉ᶬḳ℠ <vtol@gmx.net> wrote:
> On 06/02/2020 22:42, darius wrote:
> > Hello,
> > I was using meters by using 'meter' keyword, but apparently it is now
> > obsolete.
Not really, it will continue to work.
> If not mistaken the intention is to replace meter with native set / map
> syntax but meter not yet being depreciated/retired.
Yes.
> > root@HOMEROUTER:/etc/config# /etc/init.d/firewall reload
> > /etc/config/ruleset.nft:416:9-187: Error: Could not process rule: Not
> > supported
> > ct state new add @mymeter { ip saddr timeout 30s limit rate over
> > 50/second burst 50 packets } counter drop
> >
> > I'm running OpenWRT, kernel v4.14.167, nft v.0.9.2
> > Could anyone help to find out what I'm doing wrong? It seems that I did
> > it according to wiki.
Its a kernel bug. The kernel picks the wrong set backend on 4.14, so
when it sees the rule (which requires a set that supports updates) it
will fail.
Contine to use mter syntax if that works for you.
next prev parent reply other threads:[~2020-02-07 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 22:42 Metering is not working with dynamic sets on nft v0.9.2 darius
2020-02-07 9:48 ` ѽ҉ᶬḳ℠
2020-02-07 10:17 ` Florian Westphal [this message]
2020-02-07 11:00 ` Darius
2020-02-07 11:06 ` Florian Westphal
2020-02-07 11:08 ` Darius
2020-02-08 21:49 ` darius
2020-02-08 22:15 ` Florian Westphal
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=20200207101740.GC6466@breakpoint.cc \
--to=fw@strlen.de \
--cc=dram@mailbox.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.