From: Daniel Frederiksen <cyberdoc@cyberdoc.dk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Bandwidth Metering
Date: Wed, 29 Sep 2004 10:49:34 +0000 [thread overview]
Message-ID: <1096454974.13694.19.camel@hermes> (raw)
In-Reply-To: <603140b6040928154752febf20@mail.gmail.com>
Hej Patrick
Again there might be to ways I think. You could log the traffic via
libpcap or netfilter.
Netfilter could be set up to log specific traffic and afterwords you
could parse the logfile and flush it. The collected data could then be
put into a RRD base and graphed. The parsing of the logfiles is quite
simple.
Libpcap can do pretty much the same. However it might use up more CPU
and memory in the process. I guess I could whip up a perlscript that
uses libpcap to do that, if you don't know how.
There are other projects out there resembling all this, but with a lot
of other features included. Although I can't remember them at the time.
*ponders*. If it comes back to me I'll post it.
Best regards
Daniel Frederiksen, Cyberdoc.dk
On Wed, 2004-09-29 at 00:47, Patrick Coleman wrote:
> Thanks for those links. I'm building this server from scratch, so
> kernel recompiling is fine. But will these tools be able to monitor
> the bandwidth of individual users on the server itself? I realise you
> grab the apache logs to monitor bandwidth for web servers, but what
> about other services, say ssh, scp or wget? Is there an way to log the
> total amount of data passing through an interface? Is this possible?
> Thanks for your help,
> Patrick
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-09-29 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 22:47 [LARTC] Re: Bandwidth Metering Patrick Coleman
2004-09-29 10:49 ` Daniel Frederiksen [this message]
2004-09-29 11:14 ` Patrick Coleman
2004-09-29 17:09 ` Daniel Frederiksen
2004-09-29 22:45 ` Patrick Coleman
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=1096454974.13694.19.camel@hermes \
--to=cyberdoc@cyberdoc.dk \
--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.