From owner-freebsd-isp@FreeBSD.ORG Fri May 26 18:27:39 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2179616A45A for ; Fri, 26 May 2006 18:27:39 +0000 (UTC) (envelope-from ormandj@corenode.com) Received: from zone2.corenode.com (zone2.corenode.com [66.91.129.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAF6243D46 for ; Fri, 26 May 2006 18:27:38 +0000 (GMT) (envelope-from ormandj@corenode.com) Received: from corenode.com ([127.0.0.1]) by zone2.corenode.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0IZV00F06Y09HJ00@zone2.corenode.com> for freebsd-isp@freebsd.org; Fri, 26 May 2006 08:28:57 -1000 (HST) Received: from [132.160.192.10] by zone2.corenode.com (mshttpd); Fri, 26 May 2006 08:28:57 -1000 Date: Fri, 26 May 2006 08:28:57 -1000 From: "David J. Orman" In-reply-to: <44774502.7060303@wilkshire.net> To: freebsd-isp@freebsd.org Message-id: MIME-version: 1.0 X-Mailer: Sun Java(tm) System Messenger Express 6.2-3.04 (built Jul 15 2005) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en Priority: normal References: <4477250F.2@ccstores.com> <20060526155758.GA69287@energistic.com> <44774502.7060303@wilkshire.net> Subject: Re: bandwidth monitoring X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 18:27:47 -0000 SNMP is the way to go, absolutely, at the switch + possibly router level. There is no other solution that even comes close. If absolutely necessary, you can, as the previous posted mentioned, monitor the servers themselves via SNMP. This generally isn't a good idea, however, and it is best to avoid it if possible (for bandwidth monitoring.. keep in mind you can monitor cpu, memory, and lots of other nifty stuff via snmp on the servers themselves.) That being said, you'll need a way to collect data, analyze it, store it, and display it in usable means. There is again, one solution that trumps them all: http://www.cacti.net/ I know I sound really opinionated, but it really is the truth. If they ever finish the PgSQL support, it'll be pure bliss. That's the only thing about the package I don't like, the mySQL requirement. ;) Cheers, David ----- Original Message ----- From: Cody Baker Date: Friday, May 26, 2006 8:12 am Subject: Re: bandwidth monitoring > Ntop is a good tool, we use it, but my experience is that it's > buggy at > best and downright unusable at times. Also, it's data isn't very > portable. I'd recommend using SNMP data from a managed switch. If > that'snot an option the you might consider using SNMP data from > your router or > worst case directly from each individual server. In terms of software > this generally means net-snmp connected to rrdtool or mrtg. I googled > real quick and > http://www.openxtra.co.uk/resource- > center/open_source_network_monitoring.phpseems to provide a quick > front en to these tools. > > Thank You, > > Cody Baker > cody@wilkshire.net > > > Steve Ames wrote: > > ntop would work if its actually a hub. ntop would work with a switch > > also but you'd have to tell the switch to make sure that your BSD > > box gets a copy of all traffic. > > > > On Fri, May 26, 2006 at 08:55:59AM -0700, Jim Pazarena wrote: > > > >> Is there the ability to have a server which is in the common hub > >> monitor bandwidth usage of clients going out the gateway? > >> > >> My telco will shortly be changing billing practices and bandwidth > >> usage per client will be extremely important per customer. > >> > >> Is there a FreeBSD port available to do this, or must I have an > appliance>> in-line that all traffic passes thru? > >> > >> Thanks! > >> Jim > >> _______________________________________________ > >> freebsd-isp@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-isp > >> To unsubscribe, send any mail to "freebsd-isp- > unsubscribe@freebsd.org">> > > _______________________________________________ > > freebsd-isp@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > > To unsubscribe, send any mail to "freebsd-isp- > unsubscribe@freebsd.org"> > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >