All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kim Jensen <kimj@dawn.dk>
To: Bjorn Ruberg <bjorn@ruberg.no>, netfilter@lists.netfilter.org
Subject: Re: nat & ip accounting
Date: Wed, 26 Mar 2003 23:47:43 +0100	[thread overview]
Message-ID: <200303262347.43496.kimj@dawn.dk> (raw)
In-Reply-To: <1048714720.18872.13.camel@mikke>

On Wednesday 26 March 2003 22:38, Bjorn Ruberg wrote:
> On Wed, 2003-03-26 at 22:01, Kim Jensen wrote:
> > On Wednesday 26 March 2003 20:32, Alexandru Coseru wrote:
> > > Hello..
> > >
> > > I want to see using iptables -L -v  the ammount of traffic generated by
> > > each of my LAN's IP..
> > >
> > > i have masq 192.168.0.2  to 192.168.0.50...
> > >
> > > and now i want to see the traffic generated by 192.168.0.4 since the
> > > last reset of counters..
> > >
> > > How can I do that ?  I want to be able to see the download and the
> > > upload ...
> >
> > ifconfig
>
> ifconfig is the worst alternative, because it regularly resets its
> counters.
>
> As Rowan suggested, use MRTG [1] or some other tool (RRDtool [2],
> perhaps? :) to read the statistics.
>
> You may use MRTG with an SNMP daemon on your system or with an iptables
> extract script [3].
>
Well, I tried to be a little provocative with my remark on ifconfig - seems 
like it worked. MRTH is a much preferred tool. If the problem is that certain 
persons are having a very high load, then use host based limiting rules.

/Kim



  reply	other threads:[~2003-03-26 22:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 19:32 nat & ip accounting Alexandru Coseru
2003-03-26 21:01 ` Kim Jensen
2003-03-26 21:11   ` Rowan Reid
2003-03-26 21:51     ` Kim Jensen
2003-03-26 22:51       ` alexb
2003-03-26 23:17       ` Bjorn Ruberg
2003-03-26 21:38   ` Bjorn Ruberg
2003-03-26 22:47     ` Kim Jensen [this message]
2003-03-26 23:37 ` Bjorn Ruberg
2003-03-26 23:50 ` Bjorn Ruberg
     [not found] <000f01c2f3e6$8afbca60$0200a8c0@lynx>
2003-03-26 23:04 ` Rowan Reid
2003-03-27 15:04   ` Kelly Setzer

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=200303262347.43496.kimj@dawn.dk \
    --to=kimj@dawn.dk \
    --cc=bjorn@ruberg.no \
    --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 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.