From owner-freebsd-net@FreeBSD.ORG Thu Sep 9 16:22:44 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 2708D16A4CE for ; Thu, 9 Sep 2004 16:22:44 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62EDC43D49 for ; Thu, 9 Sep 2004 16:22:43 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 55133 invoked from network); 9 Sep 2004 16:19:01 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 9 Sep 2004 16:19:01 -0000 Message-ID: <4140834C.3000306@freebsd.org> Date: Thu, 09 Sep 2004 18:22:36 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a1) Gecko/20040520 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gleb Smirnoff References: <20040905121111.GA78276@cell.sick.ru> In-Reply-To: <20040905121111.GA78276@cell.sick.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: Thu, 09 Sep 2004 16:22:44 -0000 Gleb Smirnoff wrote: > Collegues, > > here is netgraph module which implements Netflow traffic > accounting, which I'm going to add to CURRENT in recent future: > > http://cell.sick.ru/~glebius/ng_netflow/ng_netflow-0.3-snap-20040905.tar.gz > > It is quite different to ng_netflow in ports/net, because its > expiry thread is running outside of netgraph context, adding > more parrallelizm on flow processing. > > I've been testing it for last week on loaded 100Mbit Ethernet > which serves 9 ASes, 12 prefixes :) And it works stable. I haven't looked into every detail but overall it's a nice piece of work. :-) In the README you are talking Netflow 5 and AS path's. I don't undestand why you want to pass the AS path into the rtentry structure? Wouldn't the right- most AS sufficise? A couple of people from OpenBSD and us are thinking of updating and extending the routing code and rtsocket framework for things like this most importantly the interaction between different routing daemons (EGP & IGP). However this is a more long-term thing and more targeted at FreeBSD 6.0. -- Andre