From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter-devel@vger.kernel.org
Subject: Re: inconsistent address treatment.
Date: Fri, 24 Dec 2010 09:20:37 +0100 [thread overview]
Message-ID: <4D1457D5.3040305@plouf.fr.eu.org> (raw)
In-Reply-To: <4D13D0FF.1010900@earthlink.net>
Stephen Clark a écrit :
> On 12/23/2010 02:52 PM, Pascal Hambourg wrote:
>>
>> Stephen Clark a écrit :
>>
>>> Why the inconsistency in the way addresses are treated. I can use -d
>>> 2.2.2.2/32
>>> but not --to-source 205.201.149.214/32
>>>
>> Because -d takes a prefix and --to-source takes an address range.
>
> So? you can't parse
>
> 205.201.149.214/32-205.201.149.218/32
a.b.c.d/32 is a prefix notation, even though it represents a single
address. IMO it does not make sense to use a prefix notation in an
interval, so I don't see why the parser should handle it. AFAICS, other
commands such as 'ip' from iproute don't accept /32 prefixes where a
single address is expected either.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-12-24 8:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 14:12 inconsistent address treatment Stephen Clark
2010-12-23 19:52 ` Pascal Hambourg
2010-12-23 22:45 ` Stephen Clark
2010-12-24 8:20 ` Pascal Hambourg [this message]
2010-12-24 15:32 ` Stephen Clark
2010-12-24 21:48 ` Jan Engelhardt
2010-12-26 12:10 ` Amos Jeffries
2010-12-26 12:47 ` Jan Engelhardt
2010-12-26 18:35 ` Stephen Clark
2010-12-26 21:43 ` Pascal Hambourg
2010-12-26 22:16 ` Jan Engelhardt
2011-01-08 4:20 ` Amos Jeffries
2011-01-08 12:32 ` Jan Engelhardt
2010-12-23 21:53 ` Jan Engelhardt
2010-12-23 22:43 ` Stephen Clark
2010-12-24 8:46 ` Jan Engelhardt
2010-12-24 15:34 ` Stephen Clark
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=4D1457D5.3040305@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).