From: Florian Westphal <fw@strlen.de>
To: Phil Sutter <phil@nwl.cc>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH v2 0/4] xt: Implement dump and restore support
Date: Thu, 17 Nov 2022 22:13:47 +0100 [thread overview]
Message-ID: <20221117211347.GB15714@breakpoint.cc> (raw)
In-Reply-To: <20221117174546.21715-1-phil@nwl.cc>
Phil Sutter <phil@nwl.cc> wrote:
> If nft can't translate a compat expression, dump it in a format that can
> be restored later without losing data, thereby keeping the ruleset
> intact.
Why? :-( This cements nft_compat.c forever.
If we're goping to do it lets at least dump it properly,
i.e. nft ... add rule compat "-m conntrack --ctstate NEW".
At this time I'd rather like a time machine to prevent nft_compat.c from
getting merged :-(
next prev parent reply other threads:[~2022-11-17 21:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 17:45 [nft PATCH v2 0/4] xt: Implement dump and restore support Phil Sutter
2022-11-17 17:45 ` [nft PATCH v2 1/4] xt: Delay libxtables access until translation Phil Sutter
2022-11-17 17:45 ` [nft PATCH v2 2/4] xt: Implement dump and restore support Phil Sutter
2022-11-17 17:45 ` [nft PATCH v2 3/4] xt: Put match/target translation into own functions Phil Sutter
2022-11-17 17:45 ` [nft PATCH v2 4/4] xt: Detect xlate callback failure Phil Sutter
2022-11-17 21:13 ` Florian Westphal [this message]
2022-11-18 9:40 ` [nft PATCH v2 0/4] xt: Implement dump and restore support Pablo Neira Ayuso
2022-11-18 9:55 ` Phil Sutter
2022-11-18 9:47 ` Phil Sutter
2022-11-18 10:11 ` Pablo Neira Ayuso
2022-11-18 10:42 ` Phil Sutter
2022-11-18 11:46 ` Florian Westphal
2022-11-18 12:12 ` Phil Sutter
2022-11-18 12:18 ` Pablo Neira Ayuso
2022-11-18 12:24 ` Phil Sutter
2022-11-18 13:34 ` Florian Westphal
2022-11-18 14:10 ` Pablo Neira Ayuso
2022-11-18 14:52 ` Phil Sutter
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=20221117211347.GB15714@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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.