From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Brskt <contact@brskt.be>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: List chain during attack high CPU usage
Date: Tue, 22 Aug 2023 11:56:26 +0200 [thread overview]
Message-ID: <ZOSGSpWQ7X6FQswi@calendula> (raw)
In-Reply-To: <em36be3a75-afb4-4570-a9eb-bcdcdf9648af@68036a95.com>
On Thu, Aug 03, 2023 at 11:49:59AM +0000, Brskt wrote:
> Hi,
>
> Is there any updates on this ?
>
> https://marc.info/?l=netfilter&m=166256224929259&w=2
>
> I don't understand why using "nft list chain netdev firewall filter" take
> time and CPU usage even if a set have a high numbers of elements since we
> don't show the elements in the set.
>
> There is the filter command in the chain "nft add rule netdev firewall
> filter update @ratelimit_test { ip saddr . ip daddr . th dport } counter
> drop" which use the set but, we don't see how many elements and/or which
> elements are in the set.
>
> Listing a chain should not try to load the elements in the set(s) that are
> used in a filter like iptables with ipset does not.
> It also do the same even if "counter" is not used.
Patch to address this issue:
https://patchwork.ozlabs.org/project/netfilter-devel/patch/20230822095324.23656-1-pablo@netfilter.org/
next prev parent reply other threads:[~2023-08-22 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 11:49 List chain during attack high CPU usage Brskt
2023-08-22 9:56 ` Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-31 0:18 Brskt
2022-09-01 10:34 ` Pablo Neira Ayuso
2022-09-07 14:54 ` Pablo Neira Ayuso
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=ZOSGSpWQ7X6FQswi@calendula \
--to=pablo@netfilter.org \
--cc=contact@brskt.be \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).