From owner-freebsd-isp Fri Aug 18 12:54:45 2000 Delivered-To: freebsd-isp@freebsd.org Received: from wopr.chc-chimes.com (wopr.chc-chimes.com [216.234.105.162]) by hub.freebsd.org (Postfix) with ESMTP id A349337B42C for ; Fri, 18 Aug 2000 12:54:41 -0700 (PDT) Received: from localhost (matta@localhost) by wopr.chc-chimes.com (8.9.3/8.9.3) with ESMTP id PAA29797; Fri, 18 Aug 2000 15:55:00 -0400 (EDT) (envelope-from matta@unixshell.com) Date: Fri, 18 Aug 2000 15:54:59 -0400 (EDT) From: matta X-Sender: matta@wopr.chc-chimes.com To: Chris Cook Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Monitoring Network Traffic In-Reply-To: <399D928C.307D9E2B@tcworks.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chris, I have had good luck using both MRTG and Cricket. I have found Cricket to provide more information for monitoring an entire network. It will let you monitor router cpu/temp/mem usage, Portmasters, BGP routing, router interfaces, switch ports and pretty much anything else with modules. I also have it monitoring FreeBSD/WindowsNT servers just fine. Cricket is in /usr/ports/net/cricket and MRTG is in /usr/ports/net/mrtg. Thanks, Matt On Fri, 18 Aug 2000, Chris Cook wrote: > Hello all, > I was wondering if anyone had some good suggestions on software that > would allow us to monitor where the majority of our backbone traffic is > being used. We have a cisco border router and FreeBSD servers... is > there some port or package that will help? Thanks in advance! > > -- > Chris > > o----< ccook@tcworks.net >-----------------------------------------o > |Chris Cook - Network Admin | TCWORKS.NET - http://www.tcworks.net | > |The Computer Works ISP | FreeBSD - http://www.freebsd.org | > o------------------------------------------------------------------o > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message