From: Patrick McHardy <kaber@trash.net>
To: Patrick McHardy <kaber@trash.net>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Roman Tsisyk <roman@tsisyk.com>,
Stig Thormodsrud <stig@vyatta.com>,
netfilter-devel@vger.kernel.org, netf
Subject: Re: NetFlow / sFlow / IPFIX network probe proposal
Date: Thu, 01 Apr 2010 16:55:09 +0200 [thread overview]
Message-ID: <4BB4B3CD.3010604@trash.net> (raw)
In-Reply-To: <20100401144617.GG19153@mail.eitzenberger.org>
Holger Eitzenberger wrote:
> On Thu, Apr 01, 2010 at 04:33:10PM +0200, Patrick McHardy 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.
>>>>
>> Adding DSCP doesn't work since we don't distinguish connections
>> by that.
>>
>
> That patch would be easy, but I was unsure at that time whether DSCP was a
> "flow characteristic" enough, especially as you have something like the
> Netfilter DSCP target to modify it, and that possibly be done not from
> the very start of a flow.
>
We certainly can't add it to the conntrack tuple, so I'm not sure
how that patch would work. But I'll gladly review it in case someone
takes a stab at this :)
next prev parent reply other threads:[~2010-04-01 14:55 UTC|newest]
Thread overview: 15+ 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
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 [this message]
2010-04-01 16:56 ` Jan Engelhardt
2010-04-08 14:55 ` Florian Weimer
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=4BB4B3CD.3010604@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@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 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).