From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (lang.hm [66.167.227.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 84F413BA8E for ; Wed, 30 May 2018 20:52:45 -0400 (EDT) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id w4V0qfWS030281; Wed, 30 May 2018 17:52:41 -0700 Date: Wed, 30 May 2018 17:52:41 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: bkil cc: make-wifi-fast@lists.bufferbloat.net In-Reply-To: Message-ID: References: User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 May 2018 00:52:45 -0000 On Sat, 19 May 2018, bkil wrote: > In reply to this thread: > https://lists.bufferbloat.net/pipermail/make-wifi-fast/2018-April/001787.html > > Sorry for the late response, although I can see from yesterday's > SmokePing plots that the issue still prevails. > > 1. > You should definitely not allow rates as low as 1Mb/s considering: > * plots of signal vs. rate, > * topology of closely packed cabins; > * mostly static, noise-free camp ground. > > Almost all of your clients were able to link with >20Mb/s even at > 70-80dBm. Those below were probably just idling. I'd limit the network > to 802.11g/n-only, and would even consider disabling all rates below > 12Mb/s. I have been wanting to do this on my APs for Scale (wndr3800 APs with ath9k chipsets) and have been unable to find how to do this on these chipsets. David Lang