Release Notes for Alpine 3.19.0: Difference between revisions
(init) |
(expand on save) |
||
| Line 4: | Line 4: | ||
the <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. this means they use the nftables kernel backend instead of the legacy iptables one. | the <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. this means they use the nftables kernel backend instead of the legacy iptables one. | ||
since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install <code>iptables-legacy</code> and use <code>iptables-legacy-save</code>. | |||
because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading. | because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading. | ||
Revision as of 15:40, 10 June 2023
Base System
iptables-nft
the /sbin/iptables{,-save,-restore} symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. this means they use the nftables kernel backend instead of the legacy iptables one.
since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install iptables-legacy and use iptables-legacy-save.
because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading.