Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Matt Taggart <matt@lackof.org>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
	Joe Touch <touch@isi.edu>
Subject: Re: [Cerowrt-devel] failing to find the "declared victory" in a current wifi router
Date: Tue, 07 Jul 2015 11:19:11 -0700	[thread overview]
Message-ID: <20150707181911.7759D208@taggart.lackof.org> (raw)
In-Reply-To: <8CBE744B-CE0D-4C44-A4B1-C7FB27403E1D@gmail.com>

Rich Brown writes:
> With that framework in mind, let me respond to your questions.
> 
> TL;DR - if you just want to fix your home network today and get on with your 
> life, I recommend:
> 	- OpenWrt Barrier Breaker (BB) release. As of July 2015, it's the stabl
> e version. Stay away from CC or trunk, as they're still evolving.
> 	- Install OpenWrt using the instructions at: http://wiki.openwrt.org/do
> c/howto/installopenwrt
> 	- Install SQM/fq_codel  to solve bufferbloat using the instructions at:
>  http://wiki.openwrt.org/doc/howto/sqm
> 	- What router to choose? I bought the TP-Link Archer C7 v2 for ~$90 (US
> ). http://wiki.openwrt.org/toh/tp-link/tl-wdr7500 In a one-out-of-one test, i
> t seems to work well with BB, SQM works fine, and I'm happy.

This message made me realize I hadn't posted the CC+SQM HOWTO I wrote, 
maybe it will be useful,

https://we.riseup.net/lackof/openwrt

Feedback welcome.

-- 
Matt Taggart
matt@lackof.org



  reply	other threads:[~2015-07-07 18:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  1:02 Joe Touch
2015-07-07  2:23 ` Rich Brown
2015-07-07  4:22   ` Joe Touch
2015-07-07  7:20     ` Sebastian Moeller
2015-07-07 12:03       ` [Cerowrt-devel] [Bloat] " Kevin Darbyshire-Bryant
2015-07-07 14:07     ` [Cerowrt-devel] " Rich Brown
2015-07-07 18:19       ` Matt Taggart [this message]
2015-07-08  1:54         ` Rich Brown
2015-07-08 18:37         ` Joe Touch
2015-07-08 20:15           ` Sebastian Moeller
2015-07-08 20:28             ` Joe Touch
2015-07-08 22:16               ` Sebastian Moeller
2015-07-09  1:34                 ` Rich Brown
2015-07-08  0:48   ` Jim Reisert AD1C
2015-07-08  2:47     ` Dave Taht
2015-07-07  6:16 ` Mikael Abrahamsson
2015-07-07 18:34   ` Joe Touch
2015-07-10  7:03     ` Mikael Abrahamsson
2015-07-10  7:22       ` Joe Touch
2015-07-10  7:48         ` Mikael Abrahamsson
2015-07-10  8:01         ` Sebastian Moeller
2015-07-10 16:57           ` Joe Touch
2015-07-07 15:40 ` Dave Taht

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=20150707181911.7759D208@taggart.lackof.org \
    --to=matt@lackof.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richb.hanover@gmail.com \
    --cc=touch@isi.edu \
    /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