From: "John A. Sullivan III" <jsullivan@opensourcedevelopmentcorp.com>
To: subscribe <subscribe@kringstad.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: Netfilter / IPTables log anlysis
Date: Mon, 02 Aug 2004 06:36:14 -0400 [thread overview]
Message-ID: <1091442974.5209.28.camel@localhost> (raw)
In-Reply-To: <ADC32223BAAA2E4BB6F9FBCF41D11633019135@picard.kringstad.net>
On Mon, 2004-08-02 at 06:16, subscribe wrote:
> Hi lists,
> I'm looking for a good log analysis / gui for IPTables,
> I've used CheckPoint's log tracker and I wounder if there
> are some product like this for IPTables ? Since fwbuilder
> is a nice gui for iptables rules, there have to be some
> good realtime log trackers.
>
> ---
> Trond
I have not looked at http://vuurmuur.sourceforge.net/ but it sounds very
promising.
Such log monitoring and troubleshooting tools are on the road map for
ISCS (http://iscs.sourceforge.net) version 1.1. If anyone would like to
help develop it, please let me know - John
--
John A. Sullivan III
Open Source Development Corporation
Financially sustainable open source development
http://www.opensourcedevelopmentcorp.com
prev parent reply other threads:[~2004-08-02 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 10:16 Netfilter / IPTables log anlysis subscribe
2004-08-02 10:36 ` 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=1091442974.5209.28.camel@localhost \
--to=jsullivan@opensourcedevelopmentcorp.com \
--cc=netfilter@lists.netfilter.org \
--cc=subscribe@kringstad.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