netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Clark <sclark46@earthlink.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List
	<netfilter-devel@vger.kernel.org>,
	pascal.mail@plouf.fr.eu.org
Subject: Re: inconsistent address treatment.
Date: Fri, 24 Dec 2010 10:34:08 -0500	[thread overview]
Message-ID: <4D14BD70.4090007@earthlink.net> (raw)
In-Reply-To: <alpine.LNX.2.01.1012240944000.13607@obet.zrqbmnf.qr>

On 12/24/2010 03:46 AM, Jan Engelhardt wrote:
> On Thursday 2010-12-23 23:43, Stephen Clark wrote:
>    
>> On 12/23/2010 04:53 PM, Jan Engelhardt wrote:
>>      
>>> On Thursday 2010-12-23 15:12, Stephen Clark wrote:
>>>
>>>        
>>>> 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
>>>>
>>>> iptables -t nat -A POSTROUTING -o eth1 -s 10.0.128.0/17 -d 2.2.2.2/32 -j SNAT
>>>> --to-source 205.201.149.214/32
>>>>
>>>>          
>>> What inconsistency?
>>>
>>>        
>> If you try the above command you get a complaint about
>>
>> --to-source 205.201.149.214/32
>> you have to use
>> --to-source 205.201.149.214
>>      
> Ah "that" sort of "inconsensitency". No, that is not an inconsistency.
> -d takes an addr[/mask] or a addr[/prefixlen] or a list thereof, while
> -m iprange and DNAT's --to-source take addr[-addr].
>
> Each is subtly different. And documented.
> --
> 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
>
>    
Just because it is documented doesn't mean it is not inconsistent.

-- 

"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty
decreases."  (Thomas Jefferson)




      reply	other threads:[~2010-12-24 15:34 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
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 [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=4D14BD70.4090007@earthlink.net \
    --to=sclark46@earthlink.net \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pascal.mail@plouf.fr.eu.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).