Date: Thu, 09 Sep 2004 18:22:36 +0200 From: Andre Oppermann <andre@freebsd.org> To: Gleb Smirnoff <glebius@freebsd.org> Cc: net@freebsd.org Subject: Re: [TEST/REVIEW] Netflow implementation Message-ID: <4140834C.3000306@freebsd.org> In-Reply-To: <20040905121111.GA78276@cell.sick.ru> References: <20040905121111.GA78276@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4140834C.3000306>