ufw before-output rules do not count packets to loopback

Bug #255092 reported by Shiv V
4
Affects Status Importance Assigned to Milestone
ufw (Ubuntu)
Fix Released
Undecided
Jamie Strandboge
Nominated for Hardy by Serge

Bug Description

Binary package hint: ufw

possibly a typo in /etc/ufw/before.rules, line 22. shouldn't it be "-o lo" instead of "-i lo" for the before-output chain?

Ubuntu 8.04.1
ufw 0.16.2.1

Related branches

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Thank you for using Ubuntu and taking the time to report a bug. Yes, this is a typo and will be fixed in the next release of ufw. It does not however affect the functionality of ufw, as the default output chain is set to ACCEPT (so outgoing on 'lo' was always still accepted), and as such it only affects the counters (as you mentioned).

Changed in ufw:
assignee: nobody → jdstrand
status: New → Triaged
Changed in ufw:
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ufw - 0.19

---------------
ufw (0.19) intrepid; urgency=low

  * don't modify the chains when --dry-run is specified (LP: #247352)
  * add dotted netmask support
  * don't have util.py import common.py
  * normalize rules so what is added to chains and what is displayed to the
    user is consistent (LP: #237446)
  * documentation updates (LP: #247177)
  * implement port ranges (LP: #231103)
  * fix initscript to properly set default DROP when ipv6 is available and
    set to 'no' in /etc/default/ufw (LP: #251355)
  * don't give confusing output when ipv6 and/or ip6_tables is not
    available (LP: #194844)
  * update ucf historical checksums to include those in 0.16.2
  * update manpage for 'status' clarifications (LP: #251153)
  * update before*.rules to count outgoing packets on lo (LP: #255092)
  * update status output so it is more consistent with rule syntax

 -- Jamie Strandboge <email address hidden> Mon, 07 Jul 2008 16:22:45 -0400

Changed in ufw:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.