From: Florian Westphal <fw@strlen.de>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: iptables upgrade: NOT operator parser trouble
Date: Fri, 28 Jun 2013 22:20:38 +0200 [thread overview]
Message-ID: <20130628202038.GB8790@breakpoint.cc> (raw)
In-Reply-To: <3833479.1RoPgaa84s@storm>
Thomas Jarosch <thomas.jarosch@intra2net.com> wrote:
> I've found another issue after upgrading iptables from 1.4.8 to 1.4.18.
> This rule used to work:
>
> iptables -A R34 --protocol tcp --dport ! 80 -j C525
Yes, but iptables used to warn about this:
'Using intrapositioned negation (`--option ! this`) is deprecated in
favor of extrapositioned (`! --option this`).'
next prev parent reply other threads:[~2013-06-28 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 17:10 iptables upgrade: NOT operator parser trouble Thomas Jarosch
2013-06-28 20:20 ` Florian Westphal [this message]
2013-07-01 8:25 ` 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=20130628202038.GB8790@breakpoint.cc \
--to=fw@strlen.de \
--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 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.