netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: pablo@netfilter.org
Subject: [nft PATCH 0/8] nft event monitor
Date: Mon, 14 Apr 2014 12:17:03 +0200	[thread overview]
Message-ID: <20140414101634.5018.86819.stgit@nfdev.cica.es> (raw)

The following series implements a basic nftables monitor via Netlink messages.

Most of the work in first patches is related to refactorization/generalization
of code.

The final patch is the big one.

About the syntax, i'm proposing:
 % nft monitor [added|deleted] [tables|chains|sets|elements|rules] [xml|json]

The straight-forward way of test this new feature is to simply run:
 % nft monitor

Other examples:
 * report new tables in XML format
   % nft monitor added tables xml
 * report deleted elements in standar nft syntax
   % nft monitor deleted elements
 * report all added/deleted rules in JSON format
   % nft monitor rules json

Handling set/set_elems is one of the harders parts of event reporting.
I've succesfully tested many cases (maps, named sets, anon-sets..), but I guess
more tuning can be done in the future, with some additional use and testing
by the community.

Please comment.

regards.
---

Arturo Borrero Gonzalez (8):
      rule: allow to print sets in plain format
      netlink: add netlink_delinearize_set() func
      rule: generalize chain_print()
      netlink: add netlink_delinearize_chain() func
      netlink: add netlink_delinearize_table() func
      netlink: refactorize set_elem conversion from netlink
      netlink: add socket error reporting helper function
      src: add events reporting


 doc/nftables.xml   |    1 
 include/mnl.h      |    3 
 include/netlink.h  |   11 +
 include/nftables.h |    1 
 include/rule.h     |   10 +
 src/evaluate.c     |    1 
 src/mnl.c          |   45 ++-
 src/netlink.c      |  746 ++++++++++++++++++++++++++++++++++++++++++++++------
 src/parser.y       |   90 ++++++
 src/rule.c         |  163 +++++++++++
 src/scanner.l      |    5 
 11 files changed, 957 insertions(+), 119 deletions(-)

-- 
Arturo Borrero Gonzalez

             reply	other threads:[~2014-04-14 10:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 10:17 Arturo Borrero Gonzalez [this message]
2014-04-14 10:17 ` [nft PATCH 1/8] rule: allow to print sets in plain format Arturo Borrero Gonzalez
2014-04-14 10:17 ` [nft PATCH 2/8] netlink: add netlink_delinearize_set() func Arturo Borrero Gonzalez
2014-04-14 10:17 ` [nft PATCH 3/8] rule: generalize chain_print() Arturo Borrero Gonzalez
2014-04-14 10:17 ` [nft PATCH 4/8] netlink: add netlink_delinearize_chain() func Arturo Borrero Gonzalez
2014-04-14 10:17 ` [nft PATCH 5/8] netlink: add netlink_delinearize_table() func Arturo Borrero Gonzalez
2014-04-14 10:17 ` [nft PATCH 6/8] netlink: refactorize set_elem conversion from netlink Arturo Borrero Gonzalez
2014-04-14 10:17 ` [nft PATCH 7/8] netlink: add socket error reporting helper function Arturo Borrero Gonzalez
2014-04-14 10:17 ` [nft PATCH 8/8] src: add events reporting Arturo Borrero Gonzalez
2014-04-14 12:28   ` Pablo Neira Ayuso
2014-04-14 12:32 ` [nft PATCH 0/8] nft event monitor Pablo Neira Ayuso
2014-04-14 12:35   ` Patrick McHardy
2014-04-28 14:28 ` 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=20140414101634.5018.86819.stgit@nfdev.cica.es \
    --to=arturo.borrero.glez@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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).