All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: kaber@trash.net, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/3] iptables: accept multiple IP address specifications for -s, -d
Date: Sun, 07 Jun 2009 23:12:06 +0200	[thread overview]
Message-ID: <4A2C2D26.6000605@netfilter.org> (raw)
In-Reply-To: <alpine.LSU.2.00.0906061314330.22992@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Saturday 2009-06-06 08:53, Pablo Neira Ayuso wrote:
>>> 	# ip6tables -I INPUT -s 2001:db8::d,2001:db8::e -j DROP
>>>
>>> References: http://marc.info/?l=netfilter-devel&m=123929790719202&w=2
>> I think this is handy for users so I can find it useful.
>>
>> The only concern that I have with this is that it changes the existing
>> 1:1 mapping between commands and iptables rules. I mean, people may get
>> confused because of this "rule expansion" feature, they may think that
>> we natively support layer 3 address sets? Probably it's a matter of
>> documenting this.
> 
> Hence:
> 
>>> +Multiple addresses can be specified when, but this will \fBreplicate\fP the
>>                                       ^^^^
>> This sentence is incomplete? I suggest to refer to the rule expansion
>> feature.
> 
> Well, I think <b>replicate</b> hits the expansion pretty good.

To replicate means to make a copy, and this is not what this does. But,
to be frank, I really don't care.

-- 
"Los honestos son inadaptados sociales" -- Les Luthiers

  reply	other threads:[~2009-06-07 21:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 19:25 iptables: pull request June-05 Jan Engelhardt
2009-06-05 19:25 ` [PATCH 1/3] iptables: accept multiple IP address specifications for -s, -d Jan Engelhardt
2009-06-06  6:53   ` Pablo Neira Ayuso
2009-06-06 11:16     ` Jan Engelhardt
2009-06-07 21:12       ` Pablo Neira Ayuso [this message]
2009-06-08 13:50     ` Patrick McHardy
2009-06-10 12:16       ` Jan Engelhardt
2009-06-10 12:19         ` Patrick McHardy
2009-06-25 17:08         ` Jan Engelhardt
2009-07-16 14:24           ` Jan Engelhardt
2009-07-17 14:31             ` Patrick McHardy
2009-07-17 15:55               ` Jan Engelhardt
2009-06-05 19:25 ` [PATCH 2/3] DNAT/SNAT: add manpage documentation for --persistent flag Jan Engelhardt
2009-06-08 13:46   ` Patrick McHardy
2009-06-05 19:25 ` [PATCH 3/3] extensions: remove redundant casts Jan Engelhardt
2009-06-08 13:47   ` Patrick McHardy
2009-06-08 13:45 ` iptables: pull request June-05 Patrick McHardy

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=4A2C2D26.6000605@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=jengelh@medozas.de \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@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 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.