From: Thomas Koeller <thomas@koeller.dyndns.org>
To: netfilter@vger.kernel.org
Subject: ipset vs. nftables set
Date: Tue, 12 Nov 2024 15:55:13 +0100 [thread overview]
Message-ID: <45ec57eecdb93fe0d03f63702ef68ebbb79bbdc1.camel@koeller.dyndns.org> (raw)
Hi,
migrating my existing firewall setup from iptables + ipset to nftables, I ran into a problem.
The firewall uses an ipset containing ipv4 source addresses to implement a dynamic blacklist. There are multiple rules that use this
ipset, and these rules are in chains that belong to different tables. This doesn't seem to be possible with nftables sets, that
apparently always have to belong to one and only one table, is this correct? At least I couldn't figure out how to create a set that
is accessible throughout the entire ruleset.
Thomas
next reply other threads:[~2024-11-12 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 14:55 Thomas Koeller [this message]
2024-11-12 17:31 ` ipset vs. nftables set Kerin Millar
2024-11-12 17:46 ` Slavko
2024-11-12 18:14 ` Pablo Neira Ayuso
2024-11-12 18:18 ` Florian Westphal
2024-11-12 18:28 ` Pablo Neira Ayuso
2024-11-12 19:44 ` Kerin Millar
2024-11-12 19:57 ` Pablo Neira Ayuso
2024-11-12 20:23 ` Kerin Millar
2024-11-12 21:04 ` Slavko
2024-11-12 18:14 ` 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=45ec57eecdb93fe0d03f63702ef68ebbb79bbdc1.camel@koeller.dyndns.org \
--to=thomas@koeller.dyndns.org \
--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.