From owner-freebsd-isp Thu May 24 17:22:40 2001 Delivered-To: freebsd-isp@freebsd.org Received: from rgmail.regenstrief.org (rgmail.regenstrief.org [134.68.31.197]) by hub.freebsd.org (Postfix) with ESMTP id 4A86937B422 for ; Thu, 24 May 2001 17:22:37 -0700 (PDT) (envelope-from gunther@aurora.regenstrief.org) Received: from aurora.regenstrief.org (rgnout.regenstrief.org [134.68.31.38]) by rgmail.regenstrief.org (8.11.0/8.8.7) with ESMTP id f4P0PHX08140; Thu, 24 May 2001 19:25:17 -0500 Message-ID: <3B0DA5C4.357D6C63@aurora.regenstrief.org> Date: Fri, 25 May 2001 00:22:28 +0000 From: Gunther Schadow Organization: Regenstrief Institute for Health Care X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Nick Rogness Cc: Kulraj Gurm , freebsd-isp@FreeBSD.ORG Subject: Re: bandwidth tracking References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 There is ALTQ as well with altqstat. And some graphing tools around this. ALTQ is nice if you don't want to just sit there and watch you bandwidth problems but do something about them. For instance, set WFQ or class based queueing. Works beautifully. If, however, you don't want to monitor use but test available bandwidth, use tcpblast, netperf, netpipe, or, if you are interested in automated UDP-streaming test probes, use my new tool "udpblast". I need to put it up on my web site soon. regards -Gunther Nick Rogness wrote: > > 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 -- Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistent Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message