From: Andrew Beverley <andy@andybev.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org
Subject: Re: Order of match extensions
Date: Thu, 06 Oct 2011 23:34:44 +0100 [thread overview]
Message-ID: <1317940484.26402.2462.camel@andybev-desktop> (raw)
In-Reply-To: <alpine.LNX.2.01.1110062258400.26555@frira.zrqbmnf.qr>
On Thu, 2011-10-06 at 22:59 +0200, Jan Engelhardt wrote:
> On Thursday 2011-10-06 22:55, Andrew Beverley wrote:
>
> >Hi,
> >
> >Does the order of match extensions matter for iptables rules?
>
> Clearly.
Okay... so why does this rule appear to not match anything?
iptables -t mangle -A FORWARD -i eth0 -m state --state NEW \
-m statistic --mode nth --every 1 -m mark ! --mark 99 -j LOG
Is the importance of the order documented anywhere?
Thanks,
Andy
prev parent reply other threads:[~2011-10-06 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 20:55 Order of match extensions Andrew Beverley
2011-10-06 20:59 ` Jan Engelhardt
2011-10-06 22:34 ` Andrew Beverley [this message]
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=1317940484.26402.2462.camel@andybev-desktop \
--to=andy@andybev.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