All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Phil Oester <kernel@linuxace.com>
Cc: netfilter-devel@lists.netfilter.org, Harald Welte <laforge@gnumonks.org>
Subject: Re: [PATCH] disallow multiple matches of same type
Date: Mon, 20 Feb 2006 18:38:22 +0100	[thread overview]
Message-ID: <43F9FE8E.5050607@trash.net> (raw)
In-Reply-To: <20060220055421.GA10552@linuxace.com>

Phil Oester wrote:
> In latest iptables SVN, the command:
> 
> iptables -A foo -p tcp -m multiport --dport 45,47 -m multiport --sport 45:48
> 
> ends up with mangled results of:
> 
> ... multiport sports  multiport sports  tcp spts:45:48
> 
> Since at present, iptables can only handle one match of a given type
> per rule.  The below patch makes sure we disallow more than one.
> 
> This closes bugzilla #447

I think Harald already did something in this direction. Harald?

  reply	other threads:[~2006-02-20 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20  5:54 [PATCH] disallow multiple matches of same type Phil Oester
2006-02-20 17:38 ` Patrick McHardy [this message]
2006-02-20 18:31   ` Phil Oester
2006-02-20 18:49     ` Harald Welte

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=43F9FE8E.5050607@trash.net \
    --to=kaber@trash.net \
    --cc=kernel@linuxace.com \
    --cc=laforge@gnumonks.org \
    --cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.