From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Leblond <eric@inl.fr>
Cc: pyctd-dev@inl.fr, netfilter-devel@lists.netfilter.org,
netfilter@lists.netfilter.org
Subject: Re: [announce] pyctd 0.1, a connection tracking XML-RPC server
Date: Wed, 08 Nov 2006 20:42:45 +0100 [thread overview]
Message-ID: <45523335.3060604@netfilter.org> (raw)
In-Reply-To: <1162999883.8096.27.camel@localhost.localdomain>
Eric Leblond wrote:
> INL devel team is proud to announce the availability of pyctd, PYthon
> Conntrack Daemon.
>
> pyctd is a XML-RPC service for monitoring and altering Netfilter
> connections tracking for network admins.
It seems that you are producing interesting stuff for sysadmins.
> It has the following functionnalities :
> * Connection listing (with byterate of each connections)
So, I assume that you are dumping the conntrack every N seconds, I'd
like to know what is the impact of this in terms of performance on a
busy firewall (lots of conntrack entries).
> * Entries removal
> * Modification of connection mark and timeout
>
> pyctd is a free software released under GNU General Public License.
I don't know if you had the chance to have a look at conntrackd, its
statistics mode is still poor but can be improved quite easily. I want
to implement conntrack dumping in XML format via conntrackd, this can be
interesting for 3rd party apps. My impression is that this daemon would
look very similar to mine, so would you consider integrating this with
conntrackd?
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
prev parent reply other threads:[~2006-11-08 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 15:31 [announce] pyctd 0.1, a connection tracking XML-RPC server Eric Leblond
2006-11-08 19:42 ` Pablo Neira Ayuso [this message]
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=45523335.3060604@netfilter.org \
--to=pablo@netfilter.org \
--cc=eric@inl.fr \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=pyctd-dev@inl.fr \
/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