Skip to contentSkip to conversation

iptables: fix save/restore symlinks with libnftnl PACKAGECONFIG enabled

PATCH New [email protected] 1 participant 1 message Jun 4, 2024

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 iptables: fix save/restore symlinks with libnftnl PACKAGECONFIG enabled

When the libnftnl PACKAGECONFIG is enabled, the "iptables" symlink is correctly points to xtables-nft-multi, however the "iptables-save" and "iptables-restore" are still point to the xtables-legacy-multi.

So, when the "iptables" command is used it's using the nftables backend where is the "iptables-save/restore" are using the legacy backend.

This is not consistent with other distros (e.g. Ubuntu).

The issue was identified when testing the UFW firewall with nftables backend.

---
 meta/recipes-extended/iptables/iptables_1.8.10.bb | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-extended/iptables/iptables_1.8.10.bb +2 -0
index a9c88582cd..86f1335ac8 100644
@@ -73,6 +73,8 @@ do_install:append() {
     # if libnftnl is included, make the iptables symlink point to the nft-based binary by default
     if ${@bb.utils.contains('PACKAGECONFIG', 'libnftnl', 'true', 'false', d)} ; then
         ln -sf ${sbindir}/xtables-nft-multi ${D}${sbindir}/iptables 
+        ln -sf ${sbindir}/xtables-nft-multi ${D}${sbindir}/iptables-save
+        ln -sf ${sbindir}/xtables-nft-multi ${D}${sbindir}/iptables-restore
     fi
 }
 
Signature · 1 line
2.34.1