netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: luciano.coelho@nokia.com
To: kaber@trash.net
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH iptables-next 0/2] extensions: add condition match and target extensions
Date: Tue, 31 Aug 2010 10:28:57 +0300	[thread overview]
Message-ID: <1283239739-5739-1-git-send-email-luciano.coelho@nokia.com> (raw)

From: Luciano Coelho <luciano.coelho@nokia.com>

Hi,

These patches add the condition match and target extensions to the iptables
tool.  These are the corresponding user space changes for the kernel patches I
sent previously (they work regardless of whether the capabilities patch is
applied or not).

This patches should be released in the iptables tool when the condition kernel
patches are released, so they should go to the iptables-next tree.

Cheers,
Luca.

Luciano Coelho (2):
  extensions: add condition match extension
  extensions: add condition target extension.

 extensions/libxt_CONDITION.c   |  144 ++++++++++++++++++++++++++++++++++++++++
 extensions/libxt_CONDITION.man |    9 +++
 extensions/libxt_condition.c   |  128 +++++++++++++++++++++++++++++++++++
 extensions/libxt_condition.man |   10 +++
 4 files changed, 291 insertions(+), 0 deletions(-)
 create mode 100644 extensions/libxt_CONDITION.c
 create mode 100644 extensions/libxt_CONDITION.man
 create mode 100644 extensions/libxt_condition.c
 create mode 100644 extensions/libxt_condition.man


             reply	other threads:[~2010-08-31  7:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31  7:28 luciano.coelho [this message]
2010-08-31  7:28 ` [PATCH iptables-next 1/2] extensions: add condition match extension luciano.coelho
2010-08-31  7:28 ` [PATCH iptables-next 2/2] extensions: add condition target extension luciano.coelho

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=1283239739-5739-1-git-send-email-luciano.coelho@nokia.com \
    --to=luciano.coelho@nokia.com \
    --cc=kaber@trash.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).