All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: "Laurence J. Lane" <ljlane@debian.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: state match incompatibilty across versions
Date: Tue, 6 Aug 2013 15:33:54 -0700	[thread overview]
Message-ID: <20130806223354.GA20287@linuxace.com> (raw)
In-Reply-To: <CA+0KVf2e_Ce33SFJyK21LzLBhUhWzWdgaMje4ShZF7i7evGuMw@mail.gmail.com>

On Tue, Aug 06, 2013 at 02:23:44PM -0400, Laurence J. Lane wrote:
> Debian Bug#718810 reports a problem with the state match across
> iptables versions. The following rules were created with the same
> states using 1.4.14. The state information on the state match do now
> show with 1.4.19.1's iptables-save or " iptables -L". The conntrack
> match's ctstate works as expected with the upgrade.

Can't seem to reproduce the problem here:

# /usr/local/ipt1414/sbin/iptables -V
iptables v1.4.14
# /usr/local/ipt1414/sbin/iptables -A foo -m state --state RELATED,ESTABLISHED -j ACCEPT
# /usr/local/ipt1414/sbin/iptables -nvL foo
Chain foo (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED


# /usr/local/iptables/sbin/iptables -V
iptables v1.4.19.1
# /usr/local/iptables/sbin/iptables -nvL foo
Chain foo (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED


Perhaps kernel revision sensitive?

Phil

  parent reply	other threads:[~2013-08-06 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06 18:23 state match incompatibilty across versions Laurence J. Lane
2013-08-06 20:35 ` Laurence J. Lane
2013-08-06 22:33 ` Phil Oester [this message]
2013-08-08  1:28 ` Laurence J. Lane
2013-08-08  4:32   ` Phil Oester
2013-08-08 13:53     ` Laurence J. Lane

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=20130806223354.GA20287@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=ljlane@debian.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 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.