From: cc <cc@belfordhk.com>
To: George Vieira <georgev@citadelcomputer.com.au>
Cc: netfilter@lists.netfilter.org
Subject: Re: iptables log analysis tool
Date: Tue, 30 Sep 2003 10:52:30 +0800 [thread overview]
Message-ID: <3F78EFEE.5040502@belfordhk.com> (raw)
In-Reply-To: <09B04A55822EFF4DA48D2E0BB2941D4A15C3B8@wardrive.citadelcomputer.com.au>
George Vieira wrote:
>>which can generate some graphs using the log files.
>
>
> this is a small project I'm working on using php
> asier/quicker to make changes) and mysql to store the data in
> even of a reboot/etc...
>
> http://mrtg.citadelcomputer.com.au
That's quite impressive collection of graphs, George. When
I get the chance I hope to get the logging done on my
firewall. Currently it's using Snort/acid but right now
having some issues with ACID. (but that's pretty
much OT here.. :))
But what is On topic is how do you prune your logs?
Thanks
next prev parent reply other threads:[~2003-09-30 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 22:41 iptables log analysis tool George Vieira
2003-09-30 2:52 ` cc [this message]
2003-10-10 19:08 ` Arnt Karlsen
-- strict thread matches above, loose matches on Subject: below --
2003-09-29 11:40 Afshin Lamei
2003-09-29 13:29 ` rcriggs
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=3F78EFEE.5040502@belfordhk.com \
--to=cc@belfordhk.com \
--cc=georgev@citadelcomputer.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox