From: Nicolas Bouliane <nib@cookinglinux.org>
To: netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 13/18] Netfilter: Multiport revision with port ranges (replaces "mport")
Date: Wed, 05 Jan 2005 00:32:18 -0500 [thread overview]
Message-ID: <41DB7BE2.70502@cookinglinux.org> (raw)
In-Reply-To: <20050105043027.GA23546@linuxace.com>
Phil Oester wrote:
> On Wed, Jan 05, 2005 at 02:35:59PM +1100, Rusty Russell wrote:
>
>>The multiport match doesn't support ranges of ports, so a new match
>>called "mport" was written. Now we have versioning of matches and
>>targets, we can simply put this extension in multiport revision 1.
>
>
> While I agree the above is a useful change, why not also add inversion
> to multiport in the process -- as long as you're making a new revision?
> Or should that be done in revision 2?
>
> Phil
>
AFAIK iptables already support ranges of ports.
iptables -A INPUT -p tcp --sport 10:40
Cheers :)
-acidfu
next prev parent reply other threads:[~2005-01-05 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 3:35 [PATCH 13/18] Netfilter: Multiport revision with port ranges (replaces "mport") Rusty Russell
2005-01-05 4:30 ` Phil Oester
2005-01-05 5:32 ` Nicolas Bouliane [this message]
2005-01-05 5:46 ` Rusty Russell
2005-01-08 2:03 ` Phil Oester
2005-01-08 3:42 ` Herve Eychenne
2005-01-09 22:34 ` Pablo Neira
2005-01-10 2:24 ` Rusty Russell
2005-01-11 1:47 ` Herve Eychenne
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=41DB7BE2.70502@cookinglinux.org \
--to=nib@cookinglinux.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.