From: "Nishit Shah" <nishit@elitecore.com>
To: 'Jan Engelhardt' <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org
Subject: RE: sequence of matches in a single rule
Date: Sat, 17 May 2008 14:18:36 +0530 [thread overview]
Message-ID: <000101c8b7fa$cb8f91f0$62aeb5d0$@com> (raw)
In-Reply-To: <alpine.LNX.1.10.0805171032270.15590@fbirervta.pbzchgretzou.qr>
-----Original Message-----
From: jengelh@sovereign.computergmbh.de
[mailto:jengelh@sovereign.computergmbh.de] On Behalf Of Jan Engelhardt
Sent: Saturday, May 17, 2008 2:06 PM
To: Nishit Shah
Cc: netfilter@vger.kernel.org
Subject: RE: sequence of matches in a single rule
On Saturday 2008-05-17 09:21, Nishit Shah wrote:
>>>Hi,
>>> Is there any specific order in which match will take place ?
>>
>>Yes. For -m conntrack and -m mark however, it does not matter,
>>as no internal state is modified. It does matter however,
>>for example, with -m statistic --mode nth and -m quota.
>
>So, can I have that order somewhere mentioned or I need to go through
source
>code ? If I write some of my own match do I have any way to change the
match
>preference ?
This is not decided in source code. The order is defined by you when
you pass the -m options to iptables.
> The reason I am asking is, there are some matches that are CPU
>incentive and some are not. For an example I prefer -m mark to always take
>precedence before -m limit or -m hashlimit, something like that..
Correct.
Note however, that limit and hashlimit have an internal state.
Using -m mark -m hashlimit, hashlimit only gets to see packets of
a specific mark, while -m hashlimit -m mark, hashlimit gets to
see all packets, and mark only sees packets which successfully
passed hashlimit.
> Or is it more preferable to not use such thing in single rule and
>prefer 2 iptables rules for that ?
One rule is much preferred in this case.
Thanks for your explanation Jan,
Just curious what will happen in case when internal state is
modified ?
What is the sequence of match when I have,
1.) -m statistic --mode nth and -m quota
2.) -m quota and -m statistic --mode nth
3.) -m statistic --mode nth and -m state
4.) -m state and -m statistic --mode nth
Rgds,
Nishit Shah.
next prev parent reply other threads:[~2008-05-17 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 5:40 sequence of matches in a single rule Nishit Shah
2008-05-17 7:05 ` Jan Engelhardt
2008-05-17 7:21 ` Nishit Shah
2008-05-17 8:35 ` Jan Engelhardt
2008-05-17 8:48 ` Nishit Shah [this message]
2008-05-17 9:12 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000101c8b7fa$cb8f91f0$62aeb5d0$@com' \
--to=nishit@elitecore.com \
--cc=jengelh@medozas.de \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox