From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: iptables upgrade: netmask parsing trouble
Date: Wed, 8 May 2013 15:10:16 +0200 [thread overview]
Message-ID: <20130508131016.GA3921@localhost> (raw)
In-Reply-To: <1548294.4rj9RFaJ57@storm>
On Wed, May 08, 2013 at 10:17:59AM +0200, Thomas Jarosch wrote:
> Hi,
>
> I've just updated from iptables 1.4.8 to 1.4.18 (git HEAD to be precise)
> and now face some trouble with netmask parsing:
>
> This used to work with 1.4.8:
> -A foo -m policy --mode tunnel --dir in --tunnel-src 192.168.123.0/255.255.255.0 -j RETURN
>
> With git HEAD I get:
> iptables-restore v1.4.18: policy: bad value for option "--tunnel-src", or out of range (0-32)
>
>
> This of course works:
> -A foo -m policy --mode tunnel --dir in --tunnel-src 192.168.123.0/24 -j RETURN
>
> Any reason why we don't accept the full format anymore?
No. Things that used to work have to work indeed. Just sent a patch to
fix it.
Thanks for the report Thomas.
next prev parent reply other threads:[~2013-05-08 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 8:17 iptables upgrade: netmask parsing trouble Thomas Jarosch
2013-05-08 13:10 ` Pablo Neira Ayuso [this message]
2013-05-08 15:01 ` Thomas Jarosch
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=20130508131016.GA3921@localhost \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=thomas.jarosch@intra2net.com \
/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).