From: Dawid Kuroczko <qnex@atlantis.ssw.krakow.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iptables output ?
Date: Thu, 24 Oct 2002 13:32:54 +0000 [thread overview]
Message-ID: <marc-lartc-103546647528543@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103546550927610@msgid-missing>
On Thu, 24 Oct 2002, raptor wrote:
> anyone to know a tool that will display more friendly output ...
> probably a tree like structure (if no cross sections occur)...
Some time ago I've started working on something like this, only
different. ;-)
Actually it is a perl module which interfaces with IPTables (and
so far it only reads standard data, no writing and no special
matching modules...).
What is "special" about it, is that it uses ioctls to read
tables, not libipt. Reasons for it were: first of all libipt
used in a "daemon" leaks memory (some advanced hash-like magic
gets too complicated and not all memory mallocated gets freed),
secondly perl is already equipped with quite efficient means
of managing lists, etc so most of libipt's code isn't needed. :)
And having bypassed libipt gives a little bit more flexibility
(for instance, a matching module could be written as a pure
perl code, using unpack and pack functions)...
Of course most of it is a bit of my wishful thinking, but
some of it works already. Unfortunately it is available
only through anonymous cvs (far too early to release it):
cvs -d :pserver:cvs@atlantis.ssw.krakow.pl:/var/cvs co \
IPTables-perl/perliptc4
Regards,
Dawid
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-10-24 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 13:18 [LARTC] iptables output ? raptor
2002-10-24 13:32 ` Dawid Kuroczko [this message]
2002-10-25 7:46 ` raptor
2002-10-25 13:23 ` Dawid Kuroczko
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=marc-lartc-103546647528543@msgid-missing \
--to=qnex@atlantis.ssw.krakow.pl \
--cc=lartc@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 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.