Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Dave Täht" <dave@taht.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Cake] Current status and recommendations for APU2C*/ArcherC7 and ath10k platforms?
Date: Fri, 31 Mar 2017 11:16:01 -0700	[thread overview]
Message-ID: <31dd1aff-9142-1636-e421-32b3666cc873@taht.net> (raw)
In-Reply-To: <87r31fyyjb.fsf@alrua-karlstad>



On 3/30/17 1:11 AM, Toke Høiland-Jørgensen wrote:
> leetminiwheat <LeetMiniWheat@gmail.com> 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
> 

      reply	other threads:[~2017-03-31 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30  4:08 [Cerowrt-devel] " leetminiwheat
2017-03-30  8:11 ` [Cerowrt-devel] [Cake] " Toke Høiland-Jørgensen
2017-03-31 18:16   ` Dave Täht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=31dd1aff-9142-1636-e421-32b3666cc873@taht.net \
    --to=dave@taht.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox