From owner-freebsd-current@FreeBSD.ORG Thu Mar 4 05:10:09 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 0728B16A57D; Thu, 4 Mar 2004 05:10:09 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B57843D49; Thu, 4 Mar 2004 05:10:08 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i24DA1QE041509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Mar 2004 16:10:01 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i24DA0bt041505; Thu, 4 Mar 2004 16:10:00 +0300 (MSK) Date: Thu, 4 Mar 2004 16:10:00 +0300 From: Gleb Smirnoff To: James Message-ID: <20040304131000.GA41474@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , James , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org 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> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040303181034.GA58284@scylla.towardex.com> User-Agent: Mutt/1.5.6i cc: Wes Peters cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: freebsd-net@freebsd.org 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 13:10:09 -0000 On Wed, Mar 03, 2004 at 01:10:34PM -0500, James wrote: J> > Currently I'm working on my Netflow implementation, and I have faced the J> > following problem: I've already got global routing in my routing table, but it J> > lacks AS (Autonomous System) information. The routing daemon (zebra in my case) J> > already knows ASes, but this informations is lost when routing information is J> > injected into kernel. It'll be nice to add AS path to struct rtentry. J> > Seems like there is no problem with extending struct rtentry, but injecting J> > this info from userland requires changes to routing API. I see two ways of J> > implementing it: J> 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. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE