iptables: regression in 1.8.9 with -n breaks portblock in resource-agents

Bug #2067274 reported by Christoph Böhmwalder
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
iptables
Fix Released
Unknown
iptables (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

In iptables 1.8.9, a regression was introduced that changes the behavior of the -n flag.

Previously, supplying -n would *not* display numerical values for the "prot" column of the -L output:

# iptables --version
iptables v1.8.7 (nf_tables)

# iptables -nL
Chain LIBVIRT_OUT (1 references)
target prot opt source destination
ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53

However, with the faulty patch, this changed to numerical values:

# iptables --version
iptables v1.8.9 (legacy)

# iptables -nL
Chain LIBVIRT_OUT (1 references)
target prot opt source destination
ACCEPT 17 -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53
ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53

This breaks parsing in the resource-agents package, namely the portblock resource agent.
Parsing has since been relaxed in resource-agents: https://github.com/ClusterLabs/resource-agents/pull/1924 (released in resource-agents v4.14.0).

There is an upstream bug report:
https://bugzilla.netfilter.org/show_bug.cgi?id=1729

For reference, there is also a report with the Debian project: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067733

The offending commit was reverted upstream:
https://git.netfilter.org/iptables/commit/?id=34f085b1607364f4eaded1140060dcaf965a2649

But the revert has not been released yet.

Ubuntu Noble ships version 1.8.10 of iptables, which is still affected. The solution would be to apply the reverted patch mentioned above.

description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in iptables (Ubuntu):
status: New → Confirmed
Changed in iptables:
status: Unknown → Confirmed
Changed in iptables:
status: Confirmed → 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.