All of lore.kernel.org
 help / color / mirror / Atom feed
From: "epankala@cc.hut.fi" <epankala@cc.hut.fi>
To: netfilter@lists.netfilter.org
Subject: xtables monitoring via NETLINK (or similar)
Date: Tue, 02 Jan 2007 20:04:34 +0200	[thread overview]
Message-ID: <459A9EB2.1000809@cc.hut.fi> (raw)


I have been looking into how kernel supplies userspace with what is
happening inside kernel via NETLINK socket and how udevd->hald->dbus->user
benefits from it.
(NETLINK_ROUTE protocol reports for example interface up/down events
and KOBJECT report device add/remove && insmod/rmmod events)


I was wondering is there a way to monitor iptables (xtables)
replace_table/(un)register_target/...  events somehow.
(could not see it in kernel code but that doesn't mean it's not there.
NETLINK_FIREWALL seems to be about queuing packets to userspace)

Main incentive for me is that it would be better to listen for a socket 
than
poll for firewall changes manually.

If such does not exist would there be intrest to add such capability.
I could volunteer to do bit of design/implementation if such feature 
would be welcomed.

-- 
Janne (orshouldthisgotonetfilter-devel) Pänkälä



                 reply	other threads:[~2007-01-02 18:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=459A9EB2.1000809@cc.hut.fi \
    --to=epankala@cc.hut.fi \
    --cc=netfilter@lists.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 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.