From owner-freebsd-isp Wed May 23 21:20: 7 2001 Delivered-To: freebsd-isp@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id 20BD437B422 for ; Wed, 23 May 2001 21:20:03 -0700 (PDT) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f4O5ZMV03897; Thu, 24 May 2001 00:35:22 -0500 (CDT) (envelope-from nick@rogness.net) Date: Thu, 24 May 2001 00:35:22 -0500 (CDT) From: Nick Rogness X-Sender: nick@cody.jharris.com To: Kulraj Gurm Cc: freebsd-isp@FreeBSD.ORG Subject: Re: bandwidth tracking In-Reply-To: <002201c0e3f0$7412cfe0$6500000a@kulraj> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 23 May 2001, Kulraj Gurm wrote: > What is the best way to track bandwidth? Any and all ideas welcome. > Can bridging help? > > What we have is : > > 1. Cisco router on wall supplied by telco > 2. Main FreeBSD 4.3-Stable box hosting client sites, three NIC's in > this machine > i. First to switch connected to cisco > ii. Second to switch serving our internal 10.0.0.0/24 network > iii. Third doing nothing yet ............. - been thinking > about bridging for a while. > 3. co-lo client boxes, for which we need to monitor traffic - these > can be attached to first switch or whatever seems to be the best way MRTG. A great little graphic bandwidth reporting package. It's in the ports. There is also a neat little shell script, bandwidth tool that someone (I think DES) posted to the list a while ago. It involved netstat in combination with another graphic building app (can't recall the name). Nick Rogness - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message