All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Ruberg <bjorn@ruberg.no>
To: netfilter@lists.netfilter.org
Subject: Re: nat & ip accounting
Date: 27 Mar 2003 00:17:54 +0100	[thread overview]
Message-ID: <1048720674.18872.19.camel@mikke> (raw)
In-Reply-To: <200303262251.45912.kimj@dawn.dk>

On Wed, 2003-03-26 at 22:51, Kim Jensen wrote:
> On Wednesday 26 March 2003 22:11, Rowan Reid wrote:
> > I have an answer but you also got me thinking.  A good tool to keep
> > track of traffic via ip addresses would be mrtg. However is there an
> > mrtg type tool that uses the counters in iptables rules to keep track of
> > traffic and output it in a user friendly form.
> 
> If you wish to see things in a more user friendly way (or usable way, as no 
> system is friendly :-) can be hard as you have to define what in what you 
> wish to see things!
> 
> mrtg is quite good, since you get the results on a webpage, but for tracking 
> ip specific things - I don't know, as I don't think the kernel remembers this 
> statistic. You can read per interface but not from each ip connecting to an 
> interface.

You can indeed log from each IP connecting. In fact you may read
whatever you configure iptables to log. You may end up with one heck of
a ruleset, as you need one iptables rule for every different parameter
you want to log.


Bjørn



  parent reply	other threads:[~2003-03-26 23:17 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 [this message]
2003-03-26 21:38   ` Bjorn Ruberg
2003-03-26 22:47     ` Kim Jensen
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=1048720674.18872.19.camel@mikke \
    --to=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.