From owner-freebsd-net@FreeBSD.ORG Thu Sep 9 17:10:22 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 4DC0716A4CE; Thu, 9 Sep 2004 17:10:22 +0000 (GMT) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8239943D2F; Thu, 9 Sep 2004 17:10:21 +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 i89HAJbN011587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Sep 2004 21:10:19 +0400 (MSD) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id i89HAJ6l011586; Thu, 9 Sep 2004 21:10:19 +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 21:10:18 +0400 From: Gleb Smirnoff To: Andre Oppermann Message-ID: <20040909171018.GA11540@cell.sick.ru> References: <20040905121111.GA78276@cell.sick.ru> <4140834C.3000306@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4140834C.3000306@freebsd.org> 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: Thu, 09 Sep 2004 17:10:22 -0000 On Thu, Sep 09, 2004 at 06:22:36PM +0200, Andre Oppermann wrote: A> I haven't looked into every detail but overall it's a nice piece of work. A> :-) Thanks :) A> In the README you are talking Netflow 5 and AS path's. I don't undestand A> why A> you want to pass the AS path into the rtentry structure? Wouldn't the A> right-most AS sufficise? AFAIK, Cisco's netflow can be configured in two modes: "peer-as", when a left-most is put into exports, and "orig-as" when a right-most is put. "orig-as" mode is default one, since most interesting statistics can be taken from it. However, "peer-as" is used for billing purposes, when we need to know which peer was transit for this traffic. A> A couple of people from OpenBSD and us are thinking of updating and A> extending A> the routing code and rtsocket framework for things like this most A> importantly A> the interaction between different routing daemons (EGP & IGP). However A> this is A> a more long-term thing and more targeted at FreeBSD 6.0. I'm working on a patch, which will bring AS path support. AS paths are going to be stored separately from rtentries. The latter will have a reference to AS paths. Each AS path is going to have a reference counter in self. This feature is going to be utilized not only for Netflow, but also in ipfw/dummynet. I think it would be very nice to shape bandwidth or make policy routing decisions using AS path regexes in ipfw rules. P.S. And we should keep an eye on XORP. It is young now, but is going to be a BSD-licensed alternative to zebra. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE