From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/3] Introduce aliases for matches and targets
Date: Wed, 30 Jan 2013 21:56:11 +0100 [thread overview]
Message-ID: <20130130205611.GA3287@localhost> (raw)
In-Reply-To: <1359405175-4394-1-git-send-email-kadlec@blackhole.kfki.hu>
Hi Jozsef,
On Mon, Jan 28, 2013 at 09:32:52PM +0100, Jozsef Kadlecsik wrote:
> The next patches introduce the alias support for matches and targets in
> iptables. The goal is to keep the old syntax of matches/targets merged
> into "super" matches/targets. This way firewall scripts can run unmodified,
> using the old extensions.
>
> The NOTRACK alias requires a new revision of the CT target (flags are checked
> in the current revision). Next follows the kernel part of the patches. Until
> the new revision is missing, instead of the warning, a notice is printed
> to the users.
I'm proposing a new version for the CT target. I wanted to merge
common code of revision 0 and 1 since time ago, then it follows the
patch to add the new flag.
> Please comment/ACK the patches.
I like this.
next prev parent reply other threads:[~2013-01-30 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 20:32 [PATCH 0/3] Introduce aliases for matches and targets Jozsef Kadlecsik
2013-01-28 20:32 ` [PATCH 1/3] Introduce match/target aliases Jozsef Kadlecsik
2013-01-28 20:32 ` [PATCH 2/3] Add the "state" alias to the "conntrack" match Jozsef Kadlecsik
2013-01-28 20:32 ` [PATCH 3/3] Add the "NOTRACK" alias to the "CT" target Jozsef Kadlecsik
2013-01-30 20:56 ` Pablo Neira Ayuso [this message]
2013-01-30 21:05 ` [PATCH 0/3] Introduce aliases for matches and targets Jozsef Kadlecsik
2013-01-30 23:43 ` Pablo Neira Ayuso
2013-01-31 19:40 ` Jozsef Kadlecsik
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=20130130205611.GA3287@localhost \
--to=pablo@netfilter.org \
--cc=kadlec@blackhole.kfki.hu \
--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.