IPtables has been removed from Debian for some time now and it has been replaced by nftables. iptables-legacy is still provided (which translates legacy iptables conf/commands to nftables) so our legacy firewall config still "just works" because we use the alternatives system to point the iptables command to iptables-legacy. The rationale for not migrating sooner was that Webmin has only provided support for iptables until relatively recently - it now supports nftables via a new webmin-nftables module.
So we should migrate our config to the new standard as I imagine that at some point iptables-legacy will disappear. And even before then it seems likely that new TurnKey users used to modern Linux are using nftables and may not expect our legacy config - potentially causing confusion.
OTTOMH the config that will need to change is:
I have pinned this to the 19.1 milestone for now, but assuming that the current functionality remains relevant and functional for the lifetime of 19.x (can't imagine why it won't), it may get pushed back to 20.0.
IPtables has been removed from Debian for some time now and it has been replaced by
nftables.iptables-legacyis still provided (which translates legacyiptablesconf/commands tonftables) so our legacy firewall config still "just works" because we use thealternativessystem to point theiptablescommand toiptables-legacy. The rationale for not migrating sooner was that Webmin has only provided support foriptablesuntil relatively recently - it now supportsnftablesvia a newwebmin-nftablesmodule.So we should migrate our config to the new standard as I imagine that at some point
iptables-legacywill disappear. And even before then it seems likely that new TurnKey users used to modern Linux are usingnftablesand may not expect our legacy config - potentially causing confusion.OTTOMH the config that will need to change is:
webmin-iptablespackage withwebmin-nftables(common plan)nftableswhen setting redirect rulesI have pinned this to the
19.1milestone for now, but assuming that the current functionality remains relevant and functional for the lifetime of19.x(can't imagine why it won't), it may get pushed back to20.0.