All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Maciej Żenczykowski" <zenczykowski@gmail.com>
Cc: Jan Engelhardt <jengelh@inai.de>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Cong Wang <amwang@redhat.com>,
	netfilter-devel@vger.kernel.org,
	Patrick McHardy <kaber@trash.net>,
	"David S. Miller" <davem@davemloft.net>,
	netfilter@vger.kernel.org
Subject: Re: [Patch net-next] netfilter: remove xt_NOTRACK
Date: Tue, 4 Sep 2012 10:58:13 +0200	[thread overview]
Message-ID: <20120904085813.GA24911@1984> (raw)
In-Reply-To: <CAHo-OoyEKNM4ZL5ucrrjWGOFu6iizNBzvsKUBbd5aVtpccG0hw@mail.gmail.com>

On Mon, Sep 03, 2012 at 10:29:40PM -0700, Maciej Żenczykowski wrote:
[...]
> > Not solved:
> > 4. Since NOTRACK now always maps to CT, "-j NOTRACK"
> >    has become unusable on sufficiently old kernels.
> >    Should we even bother?
> 
> Yes, we must, otherwise distros can't upgrade to latest iptables
> without either patching or upgrading kernel.

Why not? They will upgrade and they will start using the CT target
sooner than any other, which seems good to me.
--
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

WARNING: multiple messages have this Message-ID (diff)
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Maciej Żenczykowski" <zenczykowski@gmail.com>
Cc: Jan Engelhardt <jengelh@inai.de>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Cong Wang <amwang@redhat.com>,
	netfilter-devel@vger.kernel.org,
	Patrick McHardy <kaber@trash.net>,
	"David S. Miller" <davem@davemloft.net>,
	netfilter@vger.kernel.org
Subject: Re: [Patch net-next] netfilter: remove xt_NOTRACK
Date: Tue, 4 Sep 2012 10:58:13 +0200	[thread overview]
Message-ID: <20120904085813.GA24911@1984> (raw)
In-Reply-To: <CAHo-OoyEKNM4ZL5ucrrjWGOFu6iizNBzvsKUBbd5aVtpccG0hw@mail.gmail.com>

On Mon, Sep 03, 2012 at 10:29:40PM -0700, Maciej Żenczykowski wrote:
[...]
> > Not solved:
> > 4. Since NOTRACK now always maps to CT, "-j NOTRACK"
> >    has become unusable on sufficiently old kernels.
> >    Should we even bother?
> 
> Yes, we must, otherwise distros can't upgrade to latest iptables
> without either patching or upgrading kernel.

Why not? They will upgrade and they will start using the CT target
sooner than any other, which seems good to me.
--
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

  reply	other threads:[~2012-09-04  8:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-26  6:23 [Patch net-next] netfilter: remove xt_NOTRACK Cong Wang
2012-08-26 10:42 ` Maciej Żenczykowski
2012-08-26 20:04   ` Jan Engelhardt
2012-08-26 20:04     ` Jan Engelhardt
2012-09-03  7:57     ` Cong Wang
2012-09-03  7:57       ` Cong Wang
2012-09-03  8:33       ` Oliver
2012-09-03 11:50         ` Maciej Żenczykowski
2012-09-03 15:31       ` Pablo Neira Ayuso
2012-09-03 15:31         ` Pablo Neira Ayuso
2012-09-03 19:24         ` Pablo Neira Ayuso
2012-09-04  0:14           ` Maciej Żenczykowski
2012-09-04  3:57             ` Jan Engelhardt
2012-09-04  3:57               ` Jan Engelhardt
2012-09-04  5:29               ` Maciej Żenczykowski
2012-09-04  8:58                 ` Pablo Neira Ayuso [this message]
2012-09-04  8:58                   ` Pablo Neira Ayuso
2012-09-04 15:15                   ` Jan Engelhardt
2012-09-04 15:15                     ` Jan Engelhardt
2012-09-04 15:58                     ` Pablo Neira Ayuso
2012-09-04 15:58                       ` Pablo Neira Ayuso
2012-09-04 13:58               ` Pablo Neira Ayuso
2012-09-04 13:58                 ` Pablo Neira Ayuso

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=20120904085813.GA24911@1984 \
    --to=pablo@netfilter.org \
    --cc=amwang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=jengelh@inai.de \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    --cc=zenczykowski@gmail.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.