I can confirm that the issue has been resolved in the latest release. Thanks for the help
On Wed, 21 Nov 2018, 03:12 Debian Bug Tracking System <ow...@bugs.debian.org wrote: > This is an automatic notification regarding your Bug report > which was filed against the ufw package: > > #911986: ufw is disabled on startup after the most recent update. also ufw > enable returns "ERROR: could nkt load logging rules". ufw reload tells me > that the firewall is inactive. if i run ufw status after the failed ufw > command it does show that the firewall is active but ufw reload still fails > > It has been closed by Jamie Strandboge <ja...@canonical.com>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Jamie Strandboge < > ja...@canonical.com> by > replying to this email. > > > -- > 911986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911986 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > ---------- Forwarded message ---------- > From: Jamie Strandboge <ja...@canonical.com> > To: 913112-d...@bugs.debian.org, 909163-d...@bugs.debian.org, > 911986-d...@bugs.debian.org, 912418-d...@bugs.debian.org > Cc: Debian Bug Tracking System <sub...@bugs.debian.org> > Bcc: > Date: Tue, 20 Nov 2018 15:40:04 -0600 > Subject: Re: Bug#913112: ufw all traffic blocked, icmp-type + logging > error on enable > This issue is caused be a regression in iptables 1.8.1: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912610 > > This is now addressed in iptables. Please upgrade to iptables 1.8.2-2 and > ufw > should start work again. If not, please file a new bug. > > Thanks! > > -- > Jamie Strandboge | http://www.canonical.com > > > > ---------- Forwarded message ---------- > From: Aryan <www.anuprita...@gmail.com> > To: Debian Bug Tracking System <sub...@bugs.debian.org> > Cc: > Bcc: > Date: Fri, 26 Oct 2018 21:23:54 +0100 > Subject: ufw is disabled on startup after the most recent update. also ufw > enable returns "ERROR: could nkt load logging rules". ufw reload tells me > that the firewall is inactive. if i run ufw status after the failed ufw > command it does show that the firewall is active but ufw reload still fails > Package: ufw > Version: 0.35-6 > Severity: important > Tags: a11y > > > > -- System Information: > Debian Release: buster/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386, i686 > > Kernel: Linux 4.19.0+ (SMP w/4 CPU cores) > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages ufw depends on: > ii debconf [debconf-2.0] 1.5.69 > ii iptables 1.8.1-2 > ii lsb-base 9.20170808 > ii python3 3.6.7-1 > ii ucf 3.0038 > > ufw recommends no packages. > > Versions of packages ufw suggests: > ii rsyslog 8.38.0-1+b1 > > -- Configuration Files: > /etc/default/ufw changed: > IPV6=yes > DEFAULT_INPUT_POLICY="REJECT" > DEFAULT_OUTPUT_POLICY="ACCEPT" > DEFAULT_FORWARD_POLICY="DROP" > DEFAULT_APPLICATION_POLICY="SKIP" > MANAGE_BUILTINS=no > IPT_SYSCTL=/etc/ufw/sysctl.conf > IPT_MODULES="nf_conntrack_ftp nf_nat_ftp nf_conntrack_netbios_ns" > > > -- debconf information: > ufw/allow_known_ports: > ufw/allow_custom_ports: > ufw/enable: true > * ufw/existing_configuration: >
