netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: netfilter-devel@vger.kernel.org, pablo@netfilter.org
Subject: [RFC PATCH 0/1] xtables: allow to monitor table update event
Date: Tue,  2 Oct 2012 15:06:10 +0200	[thread overview]
Message-ID: <1349183171-4136-1-git-send-email-nicolas.dichtel@6wind.com> (raw)
In-Reply-To: <1348501182-12470-1-git-send-email-nicolas.dichtel@6wind.com>

The following patch is an example of a userspace tools (in fact, iptables)
that use the new netlink API to monitor tables activity.

I will also send a patch against libnfnetlink to update linux includes with
this new feature.

Maybe another API can be used for this feature: adding a setsockopt() on an
iptc socket to enable monitoring. When a table is updated, a packet (built with
CMSG_* macro for example) can be sent over all sockets that monitor tables
acitivity (like km sockets in IPsec). I know that this socket was used only with
[g|s]etsockopt(), but this can avoid adding another netlink API.

Comments are welcome.

Regards,
Nicolas


  reply	other threads:[~2012-10-02 13:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 15:39 [PATCH] nfnetlink: add a new subsystem to advertise tables update Nicolas Dichtel
2012-10-02 13:06 ` Nicolas Dichtel [this message]
2012-10-02 13:06   ` [RFC PATCH 1/1] xtables: allow to monitor table update event Nicolas Dichtel
2012-10-02 13:07     ` [RFC PATCH] includes: add definitions of nfnl_tables Nicolas Dichtel
2012-10-15 13:10   ` [RFC PATCH 0/1] xtables: allow to monitor table update event Nicolas Dichtel
2012-10-25 12:52     ` Nicolas Dichtel
2012-10-25 17:19       ` Pablo Neira Ayuso
2012-10-26  8:05         ` Nicolas Dichtel
2012-10-26  8:44           ` 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=1349183171-4136-1-git-send-email-nicolas.dichtel@6wind.com \
    --to=nicolas.dichtel@6wind.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).