From owner-freebsd-net@FreeBSD.ORG Fri Sep 26 14:05:42 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6488C10656E2 for ; Fri, 26 Sep 2008 14:05:42 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 01E4E8FC27 for ; Fri, 26 Sep 2008 14:05:41 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 5645 invoked by uid 89); 26 Sep 2008 14:06:21 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 26 Sep 2008 14:06:20 -0000 Message-ID: <48DCEC3E.70303@ibctech.ca> Date: Fri, 26 Sep 2008 10:05:50 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: FreeBSD Net X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: netstat byte/bit confusion X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2008 14:05:42 -0000 Hey all, I'm experiencing conflicting information on throughput numbers when comparing information garnered via MRTG on a 1000Mbps HP Procurve, and netstat -h -w1 on a server connected to the switch. What I want to know is if netstat in the below case is actually displaying the info in bits, even though it is telling me the result is in bytes: amanda# netstat -h -w1 input (Total) output packets errs bytes packets errs bytes colls 109K 0 90M 200 0 14K 0 104K 0 88M 201 0 14K 0 ^C On a different server running MRTG (FBSD 7.0-STABLE), I have configured it to display in bits/s, and it is showing ~90Mbps. Which one is accurate? I'm trying to evaluate the difference between Cisco Cat 29xx 100Mb switches and this ProCurve GigE 2848 switch. So far, my results are that the 100Mb Cisco can peak and sustain a 98Mbps throughput. The Procurve, unless MRTG is wrong, and netstat output should be 90M*8, I'm far less than impressed. ...or could it be that MRTG is broken/capped at ~100Mbps calculations? Thanks for any insight, Steve