From: Brian Schang <netfilter@lists.schang.net>
To: netfilter@vger.kernel.org
Subject: Re: iptables problem: conntrack rev 2 does not support port ranges
Date: Fri, 30 Sep 2011 21:12:45 -0400 [thread overview]
Message-ID: <4E86690D.1060400@lists.schang.net> (raw)
In-Reply-To: <alpine.LNX.2.01.1109191343280.12698@frira.zrqbmnf.qr>
Hello:
On 9/19/2011 7:44 AM, Jan Engelhardt wrote:
> On Monday 2011-09-19 13:20, Brian Schang wrote:
>
>> I dug into this a little bit and discovered:
>> # iptables -A test -m conntrack -p tcp --ctorigdstport 22 -j ACCEPT
>> iptables v1.4.12.1: conntrack rev 2 does not support port ranges
>> Try `iptables -h' or 'iptables --help' for more information.
>>
>> With some Googling, I discovered that Tom Eastep had encountered the same
>> issue. He submitted a patch for iptables and Jan Engelhardt ultimately released
>> 'iptables 1.4.12.1'.
>
> (It was not me who released 1.4.12.1.)
>
> Tom Eastep's fix was only merged after that release.
My apologies -- thanks for clarifying. I misinterpreted the git history.
prev parent reply other threads:[~2011-10-01 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 11:20 iptables problem: conntrack rev 2 does not support port ranges Brian Schang
2011-09-19 11:44 ` Jan Engelhardt
2011-10-01 1:12 ` Brian Schang [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=4E86690D.1060400@lists.schang.net \
--to=netfilter@lists.schang.net \
--cc=netfilter@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.