From: Andrew Beverley <andy@andybev.com>
To: Ed W <lists@wildgooses.com>
Cc: Netfilter <netfilter@vger.kernel.org>
Subject: Re: High accuracy bandwidth accounting?
Date: Thu, 12 May 2011 01:01:13 +0100 [thread overview]
Message-ID: <1305158473.1921.358.camel@andybev-desktop> (raw)
In-Reply-To: <4DCA9D96.90002@wildgooses.com>
On Wed, 2011-05-11 at 15:30 +0100, Ed W wrote:
> On 09/05/2011 22:45, Andrew Beverley wrote:
> > I wrote a similar patch for Squid (released in V3.2), which allows
> > packets to be marked before Squid, and Squid to reapply the mark on
> > retransmission. Marks can also be applied for locally cached files. If
> > it helps the patch is at:
> >
> > http://bazaar.launchpad.net/~squid/squid/3-trunk/revision/10925
>
>
> Did you find any better way to read the packet mark than using
> conntrack? I see that's how you are doing it in the patch you reference?
>
No, I think that's the only/best way of doing it (you can't read it from
a socket). That's the advice I got from the netfilter developers anyway,
and it doesn't get much better than that.
Andy
next prev parent reply other threads:[~2011-05-12 0:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 14:12 High accuracy bandwidth accounting? Ed W
2011-05-09 21:45 ` Andrew Beverley
2011-05-09 22:07 ` Ed W
2011-05-09 22:16 ` Andrew Beverley
2011-05-09 22:49 ` Ed W
2011-05-11 14:30 ` Ed W
2011-05-12 0:01 ` Andrew Beverley [this message]
2011-05-12 22:17 ` Ed W
2011-05-12 22:27 ` Andrew Beverley
2011-05-09 23:23 ` Ed W
2011-05-14 9:23 ` Andrew Beverley
2011-05-14 13:36 ` Ed W
2011-05-14 16:29 ` Andrew Beverley
2011-05-14 22:33 ` Jan Engelhardt
2011-05-15 7:23 ` Andrew Beverley
2011-05-15 9:08 ` Jan Engelhardt
2011-05-16 6:43 ` Andrew Beverley
2011-05-16 7:23 ` Jan Engelhardt
2011-05-22 21:22 ` Andrew Beverley
2011-05-16 14:35 ` Ed W
2011-05-16 14:59 ` Jan Engelhardt
2011-05-16 16:53 ` Ed W
2011-05-14 9:48 ` Marek Kierdelewicz
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=1305158473.1921.358.camel@andybev-desktop \
--to=andy@andybev.com \
--cc=lists@wildgooses.com \
--cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).