From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [176.58.107.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4CD363B29E for ; Fri, 31 Mar 2017 14:16:06 -0400 (EDT) Received: from dair-2642.lan (c-24-6-136-103.hsd1.ca.comcast.net [24.6.136.103]) (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 E7EAB21438 for ; Fri, 31 Mar 2017 18:16:04 +0000 (UTC) To: cerowrt-devel@lists.bufferbloat.net References: <87r31fyyjb.fsf@alrua-karlstad> From: =?UTF-8?Q?Dave_T=c3=a4ht?= Message-ID: <31dd1aff-9142-1636-e421-32b3666cc873@taht.net> Date: Fri, 31 Mar 2017 11:16:01 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <87r31fyyjb.fsf@alrua-karlstad> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Cerowrt-devel] [Cake] Current status and recommendations for APU2C*/ArcherC7 and ath10k platforms? 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: Fri, 31 Mar 2017 18:16:06 -0000 On 3/30/17 1:11 AM, Toke Høiland-Jørgensen wrote: > leetminiwheat writes: > >> Apologies I haven't had time to follow recent developments but are there >> any recent bufferbloat/CAKE related news/recommendations for the APU2 >> platform? Specifically the APU2C (previous was marvell I believe) >> >> Hardware: >> APU2C4 (AMD x86_64 | 4GB | 3x i210-AT) >> WLE600VX (ath10k) >> 64GB mSATA >> >> Also have an Archer C7 V2 (ath10k) and a old WDR3800 (ath9k) still >> chugging along. >> >> Looking for an optimal Archer C7 build or recommendations if anyone >> has any experience on it. I have generally abandoned the "all in one" home router architecture - my edge gateways are apu2s (now running the lede final release - with perfect uptime thus far), and the interior wifi box is generally a centrally located ubnt-lite. I have a small problem in that my apt gets 1.5gbit down these days, and only the apu can keep up. (the ath9ks in the apu work pretty decently, but it's at the far edge of the building next to the fiber backhaul), thus a separate wifi box. ... I now can say some very nice things about the linksys ac2600 - and the edgerouter X as well - after a month of testing the lede final, I just deployed those as the main wifi unit, and main interconnect between the yurtlab and the campus. Got rid of a whole slew of cables (it used to be 3 wndr3800s connected to the wifi uplink, backup wired line and main wired link). The edgerouter X is doing POE for the wifi mesh. ... I realize that my setups no longer resemble anything normal, and I think the archer c7v2 is still a very good box, particularly with 2ghz. The ac2600 does not have the make-wifi-fast fixes in it - and has tons of latency in the 2ghz radio... but I'm all 5ghz now and only have to drive it 20 feet, and tons faster than the archer. I'm in the middle of unplugging, reflashing and rotating out all the previous era wndr3800 gear. > > The 17.01 LEDE release is great for both the C7 and the WNDR3800, and > has all the WiFi-related fixes (bufferbloat fixes and airtime fairness) > included. You'll probably need something beefier for a main gateway at > those speeds, though. Not sure about the APU2; think it is supported in > LEDE as well? > > -Toke > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel >