From owner-freebsd-questions@FreeBSD.ORG Sat Sep 8 20:27:50 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D86816A417 for ; Sat, 8 Sep 2007 20:27:50 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [66.92.130.199]) by mx1.freebsd.org (Postfix) with ESMTP id B34E313C4A5 for ; Sat, 8 Sep 2007 20:27:49 +0000 (UTC) (envelope-from tundra@tundraware.com) MailScanner-NULL-Check: 1189888066.42863@OrNpOLIWKClJx2fENovQbA Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.1/8.14.1) with ESMTP id l88KRhJh040130 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Sat, 8 Sep 2007 15:27:43 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <46E305BA.3040604@tundraware.com> Date: Sat, 08 Sep 2007 15:27:38 -0500 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: FreeBSD Mailing List References: <46E2AEA8.4060403@adempiere.org> <70e8236f0709080735p1e60453cp435f58127c7a35fd@mail.gmail.com> <46E2BCB2.9010909@adempiere.org> <84b68b3d0709081225x4fb929fck38a3265846f7b8ba@mail.gmail.com> In-Reply-To: <84b68b3d0709081225x4fb929fck38a3265846f7b8ba@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-tundraware.com-MailScanner-Information: Please contact the ISP for more information X-tundraware.com-MailScanner: Found to be clean X-tundraware.com-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Re: ADSL Bandwidth Monitoring X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tundra@tundraware.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Sep 2007 20:27:50 -0000 Amitabh Kant wrote: > On 9/8/07, Bahman M. wrote: >> I tested the connection by downloading 2~3 files simultaneously and used >> 'bmon' as Mel suggested in another reply (thanks to him). As I'd >> already guessed the RX don't get bigger than 30~40% of the expected >> bandwidth. I performed the test with some other files and there was no >> difference. >> >> Thanks, >> >> Bahman > > The bandwidth being advertised by your ISP would be the maximum > thoughput allowed on your DSL lines with multiple DSL users sharing > the same bandwidth, something that is generally known as contention > ratio. > > See this link: > http://en.wikipedia.org/wiki/Contention_ratio > > Amitabh But you should be able to hit the advertised bandwidth. To the best of my knowledge, DSL itself is NOT a shared medium. It is a point-to- point technology from your premise to the Central Office. The bandwidth *behind* the CO may be shared, but should be so large as to not be a bottleneck. My provider (Speakeasy) advertises 1.5/384 ADSL for my circuit and that is *exactly* what I get whether moving a single file or multiple files simultaneously. There are only two reasons I can think of that would prevent you from hitting full advertised bandwidth: 1) You are too far away from the CO to hold up the circuit a full speed. Most DSL bridges/routers are adaptive and will downshift to a speed where the error rate is reduced to an acceptable level. Even if you are not far away from the CO, you will also see this if the copper pair is noisy for some other reason: bad grounding, bad splicing, old wire, etc. 2) Your premise wiring is hosed. Home telephone wiring is typically utter crap for data, even on newer homes. A new run of Cat 3 cable directly from the Network Interface box on the side of the building to the jack where the DSL bridge plugs in can do wonders. Also make sure that the cable from the bridge to that jack is good - I just had one go bad and wreak havoc for a while in my office. HTH, -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/