From: Harald Welte <laforge@gnumonks.org>
To: Olaf Titz <olaf@bigred.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Counters [Re: IP Acounting Idea for 2.5]
Date: Fri, 20 Apr 2001 13:21:38 -0300 [thread overview]
Message-ID: <20010420132138.B2461@tatooine.laforge.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.33.0104152039130.1616-100000@asdf.capslock.lan> <01041708461209.00352@workshop> <20010416020732.30431.qmail@logi.cc> <20010416104310.A29075@flint.arm.linux.org.uk> <E14pSji-0000Ng-00@hunte.bigred.inka.de>
In-Reply-To: <E14pSji-0000Ng-00@hunte.bigred.inka.de>; from olaf@bigred.inka.de on Tue, Apr 17, 2001 at 12:29:30PM +0200
On Tue, Apr 17, 2001 at 12:29:30PM +0200, Olaf Titz wrote:
> > Umm, no. Counters can be resetable - you just specify that accounting
> > programs should not reset them, ever.
> >
> > The ability to reset counters is extremely useful if you're a human
> > looking at the output of iptables -L -v. (I thus far know of no one
> > who can memorise the counter values for around 40 rules).
>
> You'll get bogus accounting results unless you stop/restart the
> accounting programs every time you manually deal with the counters.
> This sounds dangerously easy to make mistakes to me.
mmh. But isn't that obvious? Every time you mess with anything (counters
or rules) of the chains/tables, your accounting program will get into
trouble, if it relies on those counters.
I don't think that it makes sense to do iptables-based accounting if you have
changes to the ruleset (counters and/or rules) at runtime. You'd have
to be very cautious what you are doing.
> Olaf
--
Live long and prosper
- Harald Welte / laforge@gnumonks.org http://www.gnumonks.org
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M-
V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)
next prev parent reply other threads:[~2001-04-20 16:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 21:53 IP Acounting Idea for 2.5 David Findlay
2001-04-16 0:21 ` Michael Clark
2001-04-16 0:40 ` Mike A. Harris
2001-04-16 22:46 ` David Findlay
2001-04-16 0:50 ` Mike A. Harris
2001-04-16 1:58 ` swds.mlowe
2001-04-16 1:24 ` Matti Aarnio
2001-04-16 2:07 ` Manfred Bartz
2001-04-16 9:43 ` Russell King
2001-04-16 22:24 ` Manfred Bartz
2001-04-17 10:29 ` Olaf Titz
2001-04-20 16:21 ` Harald Welte [this message]
2001-04-17 1:43 ` Harald Welte
2001-04-17 2:37 ` Manfred Bartz
2001-04-17 6:56 ` Henning P. Schmiedehausen
2001-04-20 16:17 ` Harald Welte
2001-04-20 21:00 ` Henning P. Schmiedehausen
2001-04-16 11:21 ` Andreas Ferber
2001-04-16 2:40 ` Dax Kelson
2001-04-17 1:39 ` Harald Welte
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=20010420132138.B2461@tatooine.laforge.distro.conectiva \
--to=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@bigred.inka.de \
/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
all inboxes | Powered by JetHome®