From owner-freebsd-net@FreeBSD.ORG Wed Sep 8 20:24:54 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 88CD816A4CE for ; Wed, 8 Sep 2004 20:24:54 +0000 (GMT) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE9AD43D31 for ; Wed, 8 Sep 2004 20:24:53 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id i88KOlhL005207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Sep 2004 00:24:48 +0400 (MSD) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id i88KOlMX005206; Thu, 9 Sep 2004 00:24:47 +0400 (MSD) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Thu, 9 Sep 2004 00:24:47 +0400 From: Gleb Smirnoff To: Julian Elischer Message-ID: <20040908202447.GA5179@cell.sick.ru> References: <20040905121111.GA78276@cell.sick.ru> <20040908103529.V97761@murphy.imp.ch> <20040908085607.GG597@cell.sick.ru> <413F4BBE.1020304@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <413F4BBE.1020304@elischer.org> User-Agent: Mutt/1.5.6i 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 20:24:54 -0000 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? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE