From: Eric Leblond <eric@regit.org>
To: Ed W <lists@wildgooses.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: How to modify conntrack accounting?
Date: Tue, 02 Apr 2013 22:46:34 +0200 [thread overview]
Message-ID: <1364935594.30922.3.camel@ice-age.regit.org> (raw)
In-Reply-To: <515B2D5B.8010807@wildgooses.com>
[-- Attachment #1: Type: text/plain, Size: 2146 bytes --]
Hello,
Le mardi 02 avril 2013 à 20:11 +0100, Ed W a écrit :
> Hi, I have a requirement to account for "bytes I pay for" over some
> link, and conntrack very nearly gives me the right answer... This link
> uses accounting somewhat like ATM, where the IP data is sliced into
> fixed size cells and you have to pay for the overhead per cell, plus the
> wasted space in the extra cell.
I'm not sure I really understood your ATM comparison but why not use the
new accounting system like described here:
https://home.regit.org/2012/07/flow-accounting-with-netfilter-and-ulogd2/
BR,
>
> I look at the latest kernel sources and all the packet size accounting
> seems to be performed in: nf_conntrack_core.c / __nf_ct_refresh_acct()
> and __nf_ct_kill_acct().
>
> I see several options:
>
> 1) Modify the accounting procedure in nf_conntrack_core.c so that
> certain connections will use a different accounting formula. However,
> how would I mark from userspace that a certain interface has this
> unusual accounting property?
>
> 2) Could/Should I produce a new netfilter module which operates per
> packet, looks up the connection object for a given packet, and then adds
> a "fudge" to the connection accounting number to correct for the effect
> of the odd packetisation? Presumably from userspace you would then
> simply create an iptables rule tagging packets out of a certain
> interface with "-m my_odd_accounting".
>
> I don't yet know how to build option 2), but it seems appealing (anyone
> got any consultancy time and want to bill me to build it?)
>
> I would appreciate feedback from those more knowledgeable? Given the
> small niche of the solution a modification to nf_conntrack_core.c is
> appealing, but I'm unsure how to indicate which are the peculiar
> interfaces, only userspace will know this.
>
> Thanks for your thoughts/hints
>
> Ed W
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2013-04-02 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 19:11 How to modify conntrack accounting? Ed W
2013-04-02 20:46 ` Eric Leblond [this message]
2013-04-02 22:45 ` Ed W
2013-04-03 9:05 ` Eric Leblond
2013-04-03 9:58 ` Ed W
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=1364935594.30922.3.camel@ice-age.regit.org \
--to=eric@regit.org \
--cc=lists@wildgooses.com \
--cc=netfilter-devel@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).