I could reproduce the issue by building git v1.8.5 and the issue was fixed after cherry-picking "iptables-nft: fix basechain policy configuration"
$ git log commit 8d985eb4eb7a23fd98b75d71179af40169144cc5 (HEAD -> bug1898547) Author: Pablo Neira Ayuso <email address hidden> Date: Fri Oct 2 13:44:36 2020 +0200
iptables-nft: fix basechain policy configuration
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.
Signed-off-by: Arturo Borrero Gonzalez <email address hidden> Signed-off-by: Pablo Neira Ayuso <email address hidden>
commit 14ac250946289e280fb09ef978a45042871275b0 (tag: v1.8.5) Author: Pablo Neira Ayuso <email address hidden> Date: Wed Jun 3 11:37:52 2020 +0200
configure: bump version for 1.8.5 release
Signed-off-by: Pablo Neira Ayuso <email address hidden>
I could reproduce the issue by building git v1.8.5 and the issue was fixed after cherry-picking "iptables-nft: fix basechain policy configuration"
$ git log d98b75d71179af4 0169144cc5 (HEAD -> bug1898547)
commit 8d985eb4eb7a23f
Author: Pablo Neira Ayuso <email address hidden>
Date: Fri Oct 2 13:44:36 2020 +0200
iptables-nft: fix basechain policy configuration
Previous to this patch, the basechain policy could not be properly nft-restore (and ip6tables- nft-restore) trying to send an
configured if it wasn't explictly set when loading the ruleset, leading
to iptables-
invalid ruleset to the kernel.
Signed-off-by: Arturo Borrero Gonzalez <email address hidden>
Signed-off-by: Pablo Neira Ayuso <email address hidden>
commit 14ac250946289e2 80fb09ef978a450 42871275b0 (tag: v1.8.5)
Author: Pablo Neira Ayuso <email address hidden>
Date: Wed Jun 3 11:37:52 2020 +0200
configure: bump version for 1.8.5 release
Signed-off-by: Pablo Neira Ayuso <email address hidden>