From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, phil@nwl.cc
Subject: Re: [iptables PATCH] iptables-nft: fix basechain policy configuration
Date: Thu, 8 Oct 2020 19:31:56 +0200 [thread overview]
Message-ID: <20201008173156.GA14654@salvia> (raw)
In-Reply-To: <160163907669.18523.7311010971070291883.stgit@endurance>
On Fri, Oct 02, 2020 at 01:44:36PM +0200, Arturo Borrero Gonzalez wrote:
> From: Pablo Neira Ayuso <pablo@netfilter.org>
>
> Previous to this patch, the basechain policy could not be properly configured if it wasn't
> explictly set when loading the ruleset, leading to iptables-nft-restore (and ip6tables-nft-restore)
> trying to send an invalid ruleset to the kernel.
I have applied this with some amendments to the test file to cover
the --noflush case. I think this is a real problem there, where you
can combine to apply incremental updates to the ruleset.
For the --flush case, I still have doubts how to use this feature, not
sure it is worth the effort to actually fix it.
We can revisit later, you can rewrite this later Phil.
next prev parent reply other threads:[~2020-10-08 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 11:44 [iptables PATCH] iptables-nft: fix basechain policy configuration Arturo Borrero Gonzalez
2020-10-02 12:07 ` Phil Sutter
2020-10-02 12:15 ` Pablo Neira Ayuso
2020-10-02 12:28 ` Phil Sutter
2020-10-02 12:47 ` Pablo Neira Ayuso
2020-10-02 13:31 ` Phil Sutter
2020-10-02 14:39 ` Pablo Neira Ayuso
2020-10-08 17:31 ` Pablo Neira Ayuso [this message]
2020-10-09 8:29 ` Phil Sutter
2020-10-09 8:50 ` Pablo Neira Ayuso
2020-10-09 9:37 ` Phil Sutter
2020-10-09 10:07 ` Reindl Harald
2020-10-09 10:14 ` Phil Sutter
2020-10-09 10:28 ` Reindl Harald
2020-10-09 10:37 ` Jozsef Kadlecsik
2020-10-09 12:04 ` Phil Sutter
2020-10-09 19:05 ` Jozsef Kadlecsik
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=20201008173156.GA14654@salvia \
--to=pablo@netfilter.org \
--cc=arturo@netfilter.org \
--cc=netfilter-devel@vger.kernel.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 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 NNTP newsgroup(s).