From owner-freebsd-net@FreeBSD.ORG Wed Sep 8 22:37:07 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D70D16A4CE; Wed, 8 Sep 2004 22:37:07 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3106543D31; Wed, 8 Sep 2004 22:37:07 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 776867A43E; Wed, 8 Sep 2004 15:37:06 -0700 (PDT) Message-ID: <413F8992.1000900@elischer.org> Date: Wed, 08 Sep 2004 15:37:06 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Gleb Smirnoff References: <20040905121111.GA78276@cell.sick.ru> <20040908103529.V97761@murphy.imp.ch> <20040908085607.GG597@cell.sick.ru> <413F4BBE.1020304@elischer.org> <20040908202447.GA5179@cell.sick.ru> In-Reply-To: <20040908202447.GA5179@cell.sick.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Patrick.Guelat@imp.ch cc: net@freebsd.org Subject: Re: [TEST/REVIEW] Netflow implementation X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2004 22:37:07 -0000 Gleb Smirnoff wrote: >On Wed, Sep 08, 2004 at 11:13:18AM -0700, Julian Elischer wrote: >J> >This is working solution, but not correct. :) >J> >To catch both directions you should feed ng_netflow with incoming traffic >J> >from all interfaces. >J> > >J> >J> using 'tee' means you are duplicating all packets. >J> shouldn't you do collection "inline? or does this NEED to have copies of >J> the packets? > >This is in my TODO and TOSEE list. I'm not yet sure that this would be better. >There are some advantages in current state: packets are processed with no delay, >and a copy is queued for netflow processing. In case of multiple interfaces >attached to netflow node we can serve them simultaneosly, without waiting for >lock on single netflow node. > >A good solution would be to send only IP and TCP header towards netflow node. >Is there a standard way to do this? > > that would be the ng_iphdr node that you are thining about writing? :-) > > >