From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Leif Sawyer <lsawyer@gci.com>
Cc: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>,
Ian.Stirling@tomcat.admin.navo.hpc.mil, root@mauve.demon.co.uk,
linux-kernel@vger.kernel.org
Subject: Re: IP Acounting Idea for 2.5
Date: Tue, 17 Apr 2001 22:37:47 +0300 [thread overview]
Message-ID: <20010417223747.M805@mea-ext.zmailer.org> (raw)
In-Reply-To: <BF9651D8732ED311A61D00105A9CA3150446DA2E@berkeley.gci.com>
In-Reply-To: <BF9651D8732ED311A61D00105A9CA3150446DA2E@berkeley.gci.com>; from lsawyer@gci.com on Tue, Apr 17, 2001 at 11:09:09AM -0800
I repeat myself, fighting is apparently so pleasant that you are stuck on
fighting over dead-end technology:
I seriously suggest that for the primary (subject given) topic
you are SERIOUSLY OFF TARGET. Look around, counting hits on
some fw rules is waste of time! (And mightly inaccurate!)
You absolutely don't want to do any sort of counting aggeration policy
control within kernel ( = FW rules ). You want to collect accounting
per flow, and send those data records to offline analysis.
No more fighting of when to clear counters, and when not.
Having used (with own custom analyzers) cisco netflow, I can say
that any sort of "count hits on access-list elements" things are
from stone-age:
http://www.cisco.com/warp/public/cc/pd/iosw/ioft/neflct/tech/napps_wp.htm
Yet another nice thing to cook up -- if I had time ...
/Matti Aarnio
next prev parent reply other threads:[~2001-04-17 19:39 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 19:09 Leif Sawyer
2001-04-17 19:37 ` Matti Aarnio [this message]
2001-04-18 13:49 ` Michael Clark
2001-04-17 22:32 ` Manfred Bartz
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 23:06 Leif Sawyer
2001-04-17 21:48 Leif Sawyer
2001-04-17 22:58 ` Manfred Bartz
2001-04-17 23:13 ` Alan Cox
2001-04-17 23:35 ` Manfred Bartz
2001-04-18 0:02 ` Alan Cox
2001-04-20 2:51 ` Ton Hospel
2001-05-01 23:13 ` Mark van Walraven
2001-04-18 8:16 ` Kenneth Johansson
2001-04-18 14:45 ` Jonathan Lundell
2001-04-17 21:25 Jesse Pollard
2001-04-17 18:31 Jesse Pollard
2001-04-17 16:57 Leif Sawyer
2001-04-17 12:28 Jesse Pollard
2001-04-16 23:52 Leif Sawyer
2001-04-16 22:35 Leif Sawyer
2001-04-16 23:42 ` Ian Stirling
2001-04-17 1:13 ` Manfred Bartz
2001-04-17 10:34 ` Olaf Titz
2001-04-16 21:53 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-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=20010417223747.M805@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=Ian.Stirling@tomcat.admin.navo.hpc.mil \
--cc=linux-kernel@vger.kernel.org \
--cc=lsawyer@gci.com \
--cc=pollard@tomcat.admin.navo.hpc.mil \
--cc=root@mauve.demon.co.uk \
/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®