While this issue is known, it is due to a regression in iptables 1.8.4 and isn't something ufw should fix. Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949518#12 for ways to workaround the issue, or downgrade to 1.8.3-2 until iptables is fixed (see http://snapshot.debian.org/package/iptables/1.8.3-2/).
I'm going to leave the ufw task as open for now so people can more readily find the bug and will close it when Debian has fixed iptables.
While this issue is known, it is due to a regression in iptables 1.8.4 and isn't something ufw should fix. Please see https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 949518# 12 for ways to workaround the issue, or downgrade to 1.8.3-2 until iptables is fixed (see http:// snapshot. debian. org/package/ iptables/ 1.8.3-2/).
I'm going to leave the ufw task as open for now so people can more readily find the bug and will close it when Debian has fixed iptables.