From: john slee <indigoid@higherplane.net>
To: Lincoln Dale <ltd@cisco.com>
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
Ben Greear <greearb@candelatech.com>,
linux-kernel@vger.kernel.org
Subject: Re: RFC: per-socket statistics on received/dropped packets
Date: Thu, 13 Jun 2002 00:52:13 +1000 [thread overview]
Message-ID: <20020612145212.GF27429@higherplane.net> (raw)
In-Reply-To: <greearb@candelatech.com> <3D06E9A0.5060801@candelatech.com> <5.1.0.14.2.20020612221925.0283fb18@mira-sjcm-3.cisco.com>
[ trimmed cc ]
On Wed, Jun 12, 2002 at 10:28:15PM +1000, Lincoln Dale wrote:
> right now, those bills are anywhere between 10% to 25% incorrect.
10-25% is roughly equivalent to the hit rates i've seen on my web caches
in real life, with MANY users. i can't believe people are actually
using this for data accounting.
i also can't think of many decent "free" (whatever your interpretation
of that is) ways to do it either. interface packet counters wrap
around, most commercial firewalls i've used have inaccurate or
incomplete logging (to put it lightly), and packet sniffers sometimes
can't keep up.
surely if profit (or just keeping your head above the water) is the goal
you can justify the necessary resources to use something like netflow, a
product designed to do exactly what you seem to want, among other
things. (search cisco.com, and no, i'm not a cisco employee)
fiddling the network stack so that you can do dubious hacks in an
allegedly apparently dubious aspect of squid just doesn't seem to be the
ideal way to fix this problem.
regards,
j.
--
toyota power: http://indigoid.net/
next prev parent reply other threads:[~2002-06-12 14:50 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 19:37 RFC: per-socket statistics on received/dropped packets Chris Friesen
2002-06-07 3:21 ` David S. Miller
2002-06-07 15:34 ` Chris Friesen
2002-06-07 22:15 ` Ben Greear
2002-06-08 21:05 ` Mark Mielke
2002-06-08 23:04 ` David S. Miller
2002-06-09 0:13 ` Ben Greear
2002-06-09 0:51 ` David S. Miller
2002-06-09 18:23 ` Ben Greear
2002-06-10 4:34 ` David S. Miller
2002-06-10 5:55 ` Mark Mielke
2002-06-10 6:08 ` Ben Greear
2002-06-10 12:03 ` Lincoln Dale
2002-06-10 12:18 ` David S. Miller
2002-06-10 12:24 ` jamal
2002-06-10 13:57 ` Mark Mielke
2002-06-10 14:45 ` jamal
2002-06-10 14:56 ` jamal
2002-06-10 19:28 ` Chris Friesen
2002-06-10 18:44 ` David Ford
2002-06-10 18:50 ` Thunder from the hill
2002-06-10 19:02 ` David Ford
2002-06-11 22:41 ` Bill Davidsen
2002-06-12 3:41 ` David S. Miller
2002-06-12 3:57 ` Richard Guy Briggs
2002-06-12 5:20 ` Mark Mielke
2002-06-12 6:08 ` Pekka Savola
2002-06-12 6:26 ` Ben Greear
2002-06-12 6:32 ` Pekka Savola
2002-06-12 6:49 ` Ben Greear
2002-06-12 12:11 ` Horst von Brand
2002-06-12 12:28 ` Lincoln Dale
2002-06-12 12:33 ` jamal
2002-06-12 12:44 ` Lincoln Dale
2002-06-12 13:00 ` jamal
2002-06-12 14:53 ` Mark Mielke
2002-06-12 15:57 ` jamal
2002-06-12 17:00 ` Horst von Brand
2002-06-14 0:24 ` Lincoln Dale
2002-06-14 15:51 ` Stephen Hemminger
2002-06-14 18:09 ` Ben Greear
2002-06-12 14:52 ` john slee [this message]
2002-06-12 14:55 ` Mark Mielke
2002-06-13 2:52 ` Lincoln Dale
2002-06-13 19:53 ` Horst von Brand
2002-06-13 7:21 ` David Schwartz
2002-06-13 8:44 ` Lincoln Dale
2002-06-13 10:10 ` David Schwartz
2002-06-23 2:03 ` Alan Cox
2002-06-23 2:05 ` Lincoln Dale
2002-06-12 9:18 ` Sean Hunter
2002-06-09 14:47 ` Pekka Pietikäinen
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=20020612145212.GF27429@higherplane.net \
--to=indigoid@higherplane.net \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltd@cisco.com \
--cc=vonbrand@inf.utfsm.cl \
/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