From mboxrd@z Thu Jan 1 00:00:00 1970 From: Holger Eitzenberger Subject: Re: NetFlow / sFlow / IPFIX network probe proposal Date: Thu, 1 Apr 2010 16:46:17 +0200 Message-ID: <20100401144617.GG19153@mail.eitzenberger.org> References: <4BB22952.2050305@trash.net> <4BB473CB.5030300@trash.net> <20100401120536.GF19153@mail.eitzenberger.org> <4BB4ADB6.4080206@netfilter.org> <4BB4AEA6.5000102@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Pablo Neira Ayuso , Roman Tsisyk , Stig Thormodsrud , netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org, linux-net@vger.kernel.org, Holger Eitzenberger To: Patrick McHardy Return-path: Received: from moutng.kundenserver.de ([212.227.17.10]:49978 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752018Ab0DAOqV (ORCPT ); Thu, 1 Apr 2010 10:46:21 -0400 Content-Disposition: inline In-Reply-To: <4BB4AEA6.5000102@trash.net> Sender: netfilter-devel-owner@vger.kernel.org List-ID: 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. /holger