From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: tommy@svearike.sytes.net
Cc: netfilter@lists.netfilter.org
Subject: Re: iptables monitoring program
Date: Tue, 04 Oct 2005 09:51:59 -0400 [thread overview]
Message-ID: <1128433919.2945.6.camel@localhost> (raw)
In-Reply-To: <200510031604.34646.tommy@svearike.sytes.net>
On Mon, 2005-10-03 at 16:04 +0200, Tommy W wrote:
> I've developed a program (under development) to monitor iptables-rules/chains
> in realtime. and I just thought that maybe you guys in here would be
> interested of it. What I do not know on the other hand is if it's "ok" to
> promote my program in here, if it's not sorry :) but I've seen other people
> doing similar things.
>
> Back to the program.
> It consists of a library and programs utilizing the library.
> The library takes care of putting speed's on the libiptc-structures.
>
> natdump -d -z will dump out all rules in the active configuration that has a
> speed of more than 0
>
> natstat is a gui (ncurses) that will show the rules/chains at real time.
>
> natstatqt is a gui (qt) that does the same (not really, it's under developed
> compared to the ncruses gui).
>
> A very commonly used and needed function is to 'temporary flush' a rule.
> Meaning with a single click you can 'temporary flush' a rule to see how much
> traffic has been sent .. and another click to unflush it.
>
> It's a perfect help-tool for control freaks :)
>
> http://freshmeat.net/projects/natstat/
>
I haven't tried it yet but it sounds like a neat tool. Thanks for
bringing it to our attention - John
--
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan@opensourcedevel.com
If you would like to participate in the development of an open source
enterprise class network security management system, please visit
http://iscs.sourceforge.net
prev parent reply other threads:[~2005-10-04 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 14:04 iptables monitoring program Tommy W
2005-10-04 13:51 ` John A. Sullivan III [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=1128433919.2945.6.camel@localhost \
--to=jsullivan@opensourcedevel.com \
--cc=netfilter@lists.netfilter.org \
--cc=tommy@svearike.sytes.net \
/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