Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Arnt Karlsen <arnt@c2i.net>
To: George Vieira <georgev@citadelcomputer.com.au>
Cc: netfilter@lists.netfilter.org
Subject: Re: Log Analyser
Date: Wed, 2 Jul 2003 01:30:15 +0200	[thread overview]
Message-ID: <20030702013015.421ad3ea.arnt@c2i.net> (raw)
In-Reply-To: <09B04A55822EFF4DA48D2E0BB2941D4A15BEAF@wardrive.citadelcomputer.com.au>

On Wed, 2 Jul 2003 08:03:22 +1000, 
"George Vieira" <georgev@citadelcomputer.com.au> wrote in message 
<09B04A55822EFF4DA48D2E0BB2941D4A15BEAF@wardrive.citadelcomputer.com.au
>:

> I rule a special chain called `-N MRTG` and store all my counters in
> there. Then I wrote my own PHP script to go through the list and
> gather the counted packets for each rule and place them into MySQL
> every 5 minutes. I then have a crontab every 5 minutes which runs MRTG
> and has targets which run my script to gather the counters..
> 
> The advantage is that reboots don't effect the counts, Monthly counts
> can be archived and reset and all sort of little things...
> 
> Oh also, I use RRDTool to graph the targets every 5 minutes too. It's
> a fiddley setup and it's not a C++ binary program but esy to make
> changes though...
> 
> Does this help you with what you need?

..an url to your tools would be very nice.

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.




  reply	other threads:[~2003-07-01 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01 22:03 Log Analyser George Vieira
2003-07-01 23:30 ` Arnt Karlsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-06 12:44 (libiptc) iptc_delete_entry or iptc_delete_num_entry? Sander Sneekes
2003-07-01 18:30 ` Log Analyser Leandro

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=20030702013015.421ad3ea.arnt@c2i.net \
    --to=arnt@c2i.net \
    --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