From owner-freebsd-net@FreeBSD.ORG Wed Sep 8 08:56:11 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 93E4616A4CE for ; Wed, 8 Sep 2004 08:56:11 +0000 (GMT) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1A643D31 for ; Wed, 8 Sep 2004 08:56:10 +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 i888u7Ge001391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Sep 2004 12:56:08 +0400 (MSD) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id i888u7mX001390; Wed, 8 Sep 2004 12:56:07 +0400 (MSD) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Wed, 8 Sep 2004 12:56:07 +0400 From: Gleb Smirnoff To: Patrick.Guelat@imp.ch Message-ID: <20040908085607.GG597@cell.sick.ru> References: <20040905121111.GA78276@cell.sick.ru> <20040908103529.V97761@murphy.imp.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040908103529.V97761@murphy.imp.ch> User-Agent: Mutt/1.5.6i 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 08:56:11 -0000 On Wed, Sep 08, 2004 at 10:43:34AM +0000, Patrick.Guelat@imp.ch wrote: P> > here is netgraph module which implements Netflow traffic P> >accounting, which I'm going to add to CURRENT in recent future: P> >[..] P> >I've been testing it for last week on loaded 100Mbit Ethernet P> >which serves 9 ASes, 12 prefixes :) And it works stable. P> P> Did some tests here, looks very nice ! At least our netflow-collector P> is happy with the data ;-) The only empty fields are ASNs :) I hope to fill them in future. P> flowctl did not work for me, to which P> node do you have to send the msg to ? I usually call node "netflow" using 'ngctl name', and then call 'flowctl netflow show'. P> I attached two netflow nodes on a tee, one right2left and one left2right P> to catch both directions. This is working solution, but not correct. :) To catch both directions you should feed ng_netflow with incoming traffic from all interfaces. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE