From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Roman Tsisyk <roman@tsisyk.com>,
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 16:33:10 +0200 [thread overview]
Message-ID: <4BB4AEA6.5000102@trash.net> (raw)
In-Reply-To: <4BB4ADB6.4080206@netfilter.org>
Pablo Neira Ayuso wrote:
> Holger Eitzenberger wrote:
>> Some bits and pieces may be missing on the kernel side if you need to
>> classify your flows though. E. g. some IPFIX Aggregrators require the
>> DSCP value for that.
>
> We can post a patch to add the missing stuff to ctnetlink.
Adding DSCP doesn't work since we don't distinguish connections
by that.
next prev parent reply other threads:[~2010-04-01 14:33 UTC|newest]
Thread overview: 19+ 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: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
2010-04-01 12:05 ` Holger Eitzenberger
2010-04-01 14:29 ` Pablo Neira Ayuso
2010-04-01 14:33 ` Patrick McHardy [this message]
2010-04-01 14:46 ` Holger Eitzenberger
2010-04-01 14:55 ` Patrick McHardy
2010-04-01 14:55 ` Patrick McHardy
2010-04-01 16:56 ` Jan Engelhardt
2010-04-08 14:55 ` Florian Weimer
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=4BB4AEA6.5000102@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=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.