[Bug 1042260] Re: physdev options cannot be inverted

[Jamie Strandboge]

This should be an ok test case:
$ for exe in iptables ip6tables ; do sudo $exe -N testme 2>/dev/null ; sudo $exe -A INPUT -j testme ; sudo $exe -A testme -m physdev ! --physdev-is-in ! --physdev-is-out ! --physdev-is-bridged ; done
iptables v1.4.12: physdev: option "--physdev-is-in" cannot be inverted.

Try `iptables -h' or 'iptables --help' for more information.
ip6tables v1.4.12: physdev: option "--physdev-is-in" cannot be inverted.

Try `ip6tables -h' or 'ip6tables --help' for more information.

Fixed:
$ for exe in iptables ip6tables ; do sudo $exe -N testme 2>/dev/null ; sudo $exe -A INPUT -j testme ; sudo $exe -A testme -m physdev ! --physdev-is-in ! --physdev-is-out ! --physdev-is-bridged ; done
$

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1042260

Title:
  physdev options cannot be inverted

Status in “iptables” package in Ubuntu:
  In Progress
Status in “iptables” source package in Precise:
  Incomplete
Status in “iptables” source package in Quantal:
  In Progress

Bug description:
  [Impact]
  This is a regression on iptables 1.4.12 (the one in precise) not allowing to invert options like ! --physdev-is-bridged. This affects at least zentyal-network, as it introduces these kind of rules when configuring a bridged network interface.

  [Fix]
  This is already fixed in 1.4.13. Also, you can find attached the patch extracted from the iptables GIT repository.

  [Test Case]

  [Regression Potential]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1042260/+subscriptions