[Bug 689] Ordering of multiple matches is unclear
bugzilla-daemon at netfilter.org
bugzilla-daemon at netfilter.org
Wed Jun 5 14:51:27 CEST 2013
https://bugzilla.netfilter.org/show_bug.cgi?id=689
Phil Oester <netfilter at linuxace.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |netfilter at linuxace.com
Summary|Ruleset counter on -m |Ordering of multiple
|recent match when recent |matches is unclear
|table OVERFLOWED. |
--- Comment #6 from Phil Oester <netfilter at linuxace.com> 2013-06-05 14:51:26 CEST ---
The manpage was updated last year (commit db1414ec) with the following:
+Specifies a match to use, that is, an extension module that tests for a
+specific property. The set of matches make up the condition under which a
+target is invoked. Matches are evaluated first to last as specified on the
+command line and work in short-circuit fashion, i.e. if one extension yields
+false, evaluation will stop.
This clarifies the reported issue with match ordering. Closing.
--
Configure bugmail: https://bugzilla.netfilter.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the netfilter-buglog
mailing list