Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: "Gáspár Lajos" <swifty@freemail.hu>
Cc: netfilter@vger.kernel.org
Subject: Re: How to use mark and connmark in one rule
Date: Fri, 24 Apr 2009 21:13:31 +0200	[thread overview]
Message-ID: <49F20F5B.1030200@plouf.fr.eu.org> (raw)
In-Reply-To: <49F1E5B8.7030907@freemail.hu>

Gáspár Lajos a écrit :
> 
> I think it is happens like this:
> 1. iptables checks the command line for matches and loads them,
> 2. every match registers its "extra_opts" in an internal table, (this 
> time connmark and mark registers the same "mark" option.)
> 3. iptables checks the remaining command line options against the table.
> 4. if the option found in the table then the match will decide the 
> option's fate (with the "parse" callback function).

Well, then I rephrase : why does iptables pass to the match options 
which are beyond the next -m ? It seems obvious to me that those options 
belong to the next matches. Is it an accepted practice to order matches 
and options randomly ? If yes, then non-exclusive matches should not be 
allowed to have the same options.

      reply	other threads:[~2009-04-24 19:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 13:32 How to use mark and connmark in one rule Tino Keitel
2009-04-24 13:37 ` Brian Austin - Standard Universal
2009-04-24 13:39   ` Brian Austin - Standard Universal
2009-05-12 13:00     ` Tino Keitel
2009-05-12 13:13       ` Pascal Hambourg
2009-04-24 13:40 ` Gáspár Lajos
2009-04-24 13:49   ` Tino Keitel
2009-04-24 13:55     ` Gáspár Lajos
2009-05-12 13:01       ` Tino Keitel
2009-04-24 14:46   ` Pascal Hambourg
2009-04-24 16:15     ` Gáspár Lajos
2009-04-24 19:13       ` Pascal Hambourg [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=49F20F5B.1030200@plouf.fr.eu.org \
    --to=pascal.mail@plouf.fr.eu.org \
    --cc=netfilter@vger.kernel.org \
    --cc=swifty@freemail.hu \
    /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