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] WNDR3800 improvements?
Date: Tue, 13 Dec 2016 20:41:18 -0800	[thread overview]
Message-ID: <374ac0b8-aee0-74bb-d6e9-7eacb43a12d2@taht.net> (raw)
In-Reply-To: <20161214005800.08268202@taggart.lackof.org>



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,
> 

  reply	other threads:[~2016-12-14  4:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14  0:58 Matt Taggart
2016-12-14  4:41 ` Dave Täht [this message]
2016-12-14  5:26   ` Aaron Wood
2016-12-20 22:34     ` Matt Taggart

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=374ac0b8-aee0-74bb-d6e9-7eacb43a12d2@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