Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Roman Tsisyk <roman@tsisyk.com>
Cc: Stig Thormodsrud <stig@vyatta.com>,
	netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
	linux-net@vger.kernel.org,
	Holger Eitzenberger <heitzenberger@astaro.com>
Subject: Re: NetFlow / sFlow / IPFIX network probe proposal
Date: Thu, 01 Apr 2010 12:22:03 +0200	[thread overview]
Message-ID: <4BB473CB.5030300@trash.net> (raw)
In-Reply-To: <n2yfaefb3f11003310647uef53fd2k518c4c8f0367adc5@mail.gmail.com>

Roman Tsisyk wrote:
> On Wed, Mar 31, 2010 at 2:06 AM, Stig Thormodsrud <stig@vyatta.com> wrote:
> On Tue, Mar 30, 2010 at 11:39 PM, Patrick McHardy <kaber@trash.net> wrote:
>> We already have conntrack and ctnetlink to gather per-connection
>> statistics, which should decrease the overhead for doing this in
>> userspace a lot. There also exists a netflow plugin for ulogd2,
>> but I'm not sure it was already submitted and merged.
>>
> 
> Thank you for pointing it out, I didn't know about conntrack support in ulogd.
> 
> As far as I understood, IPFIX output in ulogd is in a early stage and
> don't work. So, I tested ulogd + ctnetlink with null output and it
> worked very well.

IIRC Holger Eitzenberger (CCed) has done some work to make this work
properly. Maybe he can tell use more.

> CPU load was about 5-10%, and it's just nothing on this router.
> However, I'm not sure that output is correct and all flows was
> accounted. I also don't know what is about active and inactive
> timeouts in this approach.
> I'll look to ulogd_inpflow_NFCT more closely.
> 
> Patrick, decision is to optimize ctnetlink and not to make accounting
> in the kernel space?

Accounting is done in kernel space by conntrack, but aggregation should
be done in userspace in my opinion. I don't think you need a lot of
optimization, AFAIK Holger's patches already scale to large setups
very well.

  reply	other threads:[~2010-04-01 10:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 14:06 NetFlow / sFlow / IPFIX network probe proposal Roman Tsisyk
2010-03-30 14:29 ` Changli Gao
2010-03-30 14:56 ` Jan Engelhardt
2010-03-30 15:57   ` Roman Tsisyk
2010-03-30 16:07     ` Jan Engelhardt
2010-03-30 16:39   ` Patrick McHardy
2010-03-31 13:47     ` Roman Tsisyk
2010-04-01 10:22       ` Patrick McHardy [this message]
2010-04-01 12:05         ` Holger Eitzenberger
2010-04-01 14:29           ` Pablo Neira Ayuso
2010-04-01 14:33             ` Patrick McHardy
2010-04-01 14:46               ` Holger Eitzenberger
2010-04-01 14:55                 ` Patrick McHardy
     [not found]                 ` <4BB4B3CD.3010604@trash.net>
2010-04-01 16:56                   ` Jan Engelhardt
2010-04-08 14:55 ` Florian Weimer
     [not found] <22578828.43001269973644747.JavaMail.root@tahiti.vyatta.com>
2010-03-30 19:06 ` Stig Thormodsrud

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=4BB473CB.5030300@trash.net \
    --to=kaber@trash.net \
    --cc=heitzenberger@astaro.com \
    --cc=linux-net@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.org \
    --cc=roman@tsisyk.com \
    --cc=stig@vyatta.com \
    /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