This looks like a bug triggered by changes to the iptables package in Buster, as they swapped to nftables, and should be reasonably easy to fix (at least in the short term).
Odd that it wasn’t noticed in testing, but I’ll get it fixed ASAP.
This looks like a bug triggered by changes to the iptables package in Buster, as they swapped to nftables, and should be reasonably easy to fix (at least in the short term).
Odd that it wasn’t noticed in testing, but I’ll get it fixed ASAP.