From owner-freebsd-current@FreeBSD.ORG Thu Mar 4 09:25:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51A9316A4CE; Thu, 4 Mar 2004 09:25:30 -0800 (PST) Received: from mx01.bos.ma.towardex.com (a65-124-16-8.svc.towardex.com [65.124.16.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 137AC43D41; Thu, 4 Mar 2004 09:25:30 -0800 (PST) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id 06DDC2F898; Thu, 4 Mar 2004 12:25:30 -0500 (EST) Date: Thu, 4 Mar 2004 12:25:30 -0500 From: James To: Gleb Smirnoff , James , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040304172529.GA86502@scylla.towardex.com> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com> <20040304131000.GA41474@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040304131000.GA41474@cell.sick.ru> User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Fri, 05 Mar 2004 04:55:08 -0800 Subject: Re: My planned work on networking stack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2004 17:25:30 -0000 > J> why inject as_path info from userland to kernel "fib"? may be netflow turning > J> into an api that quagga can take advantage of to gather accounting information > J> is more feasible? > > James, can you please describe your idea more understandible? I can't understand > your last sentence, sorry. sorry, i wasn't writing clearly :) what i meant is, an implementation of an API for netflow gathering stats from the kernel. once you have that API, perhaps quagga can take advantage of that API, to support netflow accounting by itself, along with as path information and all that.. that was my thought initially, BUT.. actually... you can actually do this no problem using mrtd dumps and pick it up with a program via bgp device :P no need to create another api it seems :) -J -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net