From: Marc Haber <mh+netfilter@zugschlus.de>
To: Netfilter list <netfilter@vger.kernel.org>
Subject: Re: Combine ipv4 and ipv6 in a set
Date: Wed, 31 Jan 2024 11:21:12 +0100 [thread overview]
Message-ID: <ZbofGH6H_mhSfAg0@torres.zugschlus.de> (raw)
In-Reply-To: <20240130152247.0303cee7@cobra.bbbs.net>
On Tue, Jan 30, 2024 at 03:22:47PM +0200, Kim B. Heino wrote:
> > This is one of my pet peeves with nft, actually. For iptables, there
> > was tooling like ferm which made it possible to write dual-stack rule
> > sets very easily. This kind of tooling seems to be completely missing
> > in the nftables world. Am I missing something here?
>
> Foomuuri [https://github.com/FoobarOy/foomuuri] makes it easy to write
> dual-stack firewall rule set in text format. Not really ferm-like, but
> might be what you are looking for?
That looks interesting, but it is an entirely different language that
needs to be learned and understood. I will look into it. Where do the
rules created by Foomuuri end up? Can they be inspected by using nft
show tables?
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
next prev parent reply other threads:[~2024-01-31 10:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 10:17 Combine ipv4 and ipv6 in a set Daniel
2024-01-30 10:39 ` Kerin Millar
2024-01-30 12:13 ` Daniel
2024-01-30 12:59 ` Daniel
2024-01-30 13:08 ` Marc Haber
2024-01-30 13:22 ` Kim B. Heino
2024-01-31 10:21 ` Marc Haber [this message]
2024-01-31 11:22 ` Kim B. Heino
2024-01-30 15:17 ` Kerin Millar
2024-01-30 17:00 ` Slavko
2024-01-30 17:57 ` Kerin Millar
2024-01-30 19:34 ` Slavko
2024-01-30 22:05 ` Kerin Millar
2024-02-01 12:13 ` Marc Haber
2024-01-31 11:27 ` Marc Haber
2024-01-31 11:13 ` Marc Haber
2024-01-31 11:00 ` Marc Haber
2024-01-31 10:54 ` Marc Haber
2024-01-31 11:55 ` Daniel
2024-02-01 11:39 ` Marc Haber
2024-01-31 13:02 ` Kerin Millar
2024-01-31 20:23 ` Slavko
2024-01-31 22:10 ` Kerin Millar
2024-02-01 6:06 ` Kevin P. Fleming
2024-02-01 17:09 ` Kerin Millar
2024-02-01 10:50 ` Slavko
2024-02-01 12:48 ` Kerin Millar
2024-02-01 13:42 ` Slavko
2024-02-01 14:03 ` Kerin Millar
2024-01-31 22:36 ` Pablo Neira Ayuso
2024-02-01 8:22 ` Slavko
2024-02-02 1:38 ` Eric
2024-02-02 9:23 ` Pablo Neira Ayuso
2024-02-03 9:24 ` Slavko
2024-02-03 15:49 ` Eric
2024-02-05 9:47 ` Pablo Neira Ayuso
2024-02-05 17:02 ` Eric
2024-02-05 17:08 ` Pablo Neira Ayuso
2024-02-05 17:16 ` Eric
2024-02-01 11:33 ` Marc Haber
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=ZbofGH6H_mhSfAg0@torres.zugschlus.de \
--to=mh+netfilter@zugschlus.de \
--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.