Jaunty has been EOLd.
** Changed in: ufw (Ubuntu Jaunty)
Status: Triaged => Won't Fix
** Changed in: ufw (Ubuntu Jaunty)
Milestone: jaunty-updates => None
** Changed in: ufw (Ubuntu Karmic)
Milestone: karmic-updates => None
** Changed in: ufw (Ubuntu Karmic)
Status: In Pro
** Branch linked: lp:debian/ufw
** Branch linked: lp:debian/sid/ufw
** Branch linked: lp:ubuntu/ufw
--
ufw loglevels don't log after reboot
https://bugs.launchpad.net/bugs/459925
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
This bug was fixed in the package ufw - 0.29.1-1
---
ufw (0.29.1-1) unstable; urgency=low
* new upstream release, fixing LP: #459925 and LP: #480789
* debian/postinst: run 'ufw logging ' to update the user
rules for logging (this action does nothing when ufw is not enabled)
Lucid will be updated via a sync of 0.29.1-1 from Debian, once it is
available.
** Changed in: ufw (Ubuntu Karmic)
Status: Triaged => In Progress
** Changed in: ufw (Ubuntu Lucid)
Status: Triaged => In Progress
--
ufw loglevels don't log after reboot
https://bugs.launchpad.net/bug
Fixed in 0.29.1
** Changed in: ufw
Status: Fix Committed => Fix Released
--
ufw loglevels don't log after reboot
https://bugs.launchpad.net/bugs/459925
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
UPDATED TEST CASE
I forgot to enable the firewall initially and left out the 2nd iptables-save
command. Please use this test case instead:
$ sudo ufw enable
$ sudo iptables-save|grep '^-.*logging' | wc -l
12
$ sudo ufw disable
$ sudo sed -i "s/^ENABLED=.*/ENABLED=yes/" /etc/ufw/ufw.conf
$ sudo /l
TEST CASE
$ sudo iptables-save|grep '^-.*logging' | wc -l
12
$ sudo ufw disable
$ sudo sed -i "s/^ENABLED=.*/ENABLED=yes/" /etc/ufw/ufw.conf
$ sudo /lib/ufw/ufw-init start
8
While the number of lines given by 'wc' will differ depending on the
firewall configuration, the important thing is they sh
** Summary changed:
- ufw not logging packets against default policy after reboot
+ ufw loglevels don't log after reboot
** Tags removed: amd64 apport-bug
--
ufw loglevels don't log after reboot
https://bugs.launchpad.net/bugs/459925
You received this bug notification because you are a member o
