From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [IPv6:2a01:7e00::f03c:91ff:feae:7028]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 06E2B3B260 for ; Tue, 13 Dec 2016 23:41:21 -0500 (EST) Received: from dair-2506.local (wsip-184-177-182-40.oc.oc.cox.net [184.177.182.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id CCEBD21434 for ; Wed, 14 Dec 2016 04:41:20 +0000 (UTC) To: cerowrt-devel@lists.bufferbloat.net References: <20161214005800.08268202@taggart.lackof.org> From: =?UTF-8?Q?Dave_T=c3=a4ht?= Message-ID: <374ac0b8-aee0-74bb-d6e9-7eacb43a12d2@taht.net> Date: Tue, 13 Dec 2016 20:41:18 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161214005800.08268202@taggart.lackof.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Cerowrt-devel] WNDR3800 improvements? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 04:41:22 -0000 On 12/13/16 4:58 PM, Matt Taggart wrote: > Hi, > > I love the WNDR3800 platform, it's been great over the years first with > cerowrt and then openwrt. Of the many I've deployed I have only had > hardware problems with 2 of them, and usually uptimes go over 100 days. You > can also still buy them used for $20 w/free shipping on amazon! > > With the recent improvement for cake, make-wifi-fast, driver improvements, > etc is there any chance in seeing some of these things land for the > WNDR3800 specifically? It would be really nice if this hardware could > continue to do SQM, etc for some of the faster broadband speeds the cable > providers are offering (comcast xfinity has 100, 200, 250 plans now) and > see some of the wifi improvements too. We already support the 3800, although it peaks at 60 mbits of inbound rate shaping. If your primary use case is wifi, with the latest fq_codel code, you can live without inbound shaping and probably get 150mbits well managed. > > Thanks, >