Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] CeroWrt bits not in OpenWrt (renamed thread)
Date: Thu, 12 Mar 2015 20:43:49 +0000	[thread overview]
Message-ID: <5501FA85.7020107@gmail.com> (raw)
In-Reply-To: <5501F7B7.9040105@gmail.com>

On 12/03/15 20:31, Alan Jenkins wrote:
> On 12/03/15 16:43, Rich Brown wrote:
>> - BB seems to have bloat, and I don't understand how to install and
>> configure the QoS/SQM scripts.
>
> Install qos-scripts package.  package install requires first updating, 
> since package cache does not persist over reboots. Pleasantly that 
> detail isn't too obscure in luci System -> Software.  "Update lists" 
> button is at the top & there's a neighboring label saying "No package 
> lists available".
>
> The install doesn't automatically enable the `qos` init script. Maybe 
> it's a general policy like how Fedora treats daemons.  You must
>
> `/etc/init.d/qos enable`, or use luci System -> Startup
>
>> (And is there a Luci GUI?)
>
> luci-app-qos.  Installing that package will pull in qos-scripts for 
> you.  It's an easy way to enable qos.  qos is disabled by default... 
> which made three steps so far just to enable it. Though I suppose you 
> need to enter the upload / download speed here anyway, before it can 
> sensibly be enabled.

Gah, that was stupidly unclear.  I mean

1. luci-app-qos gives you a nice page under Network -> QOS.

2. There's a config to enable qos, separate from enabling the init 
script, after you've installed qos-scripts.  It's a pity it's not just 
enabled once you start the init script.  luci could just give you a 
button on the QOS page to enable/disable the init script (and start/stop 
at the same time!).  Job done.

  reply	other threads:[~2015-03-12 20:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 18:15 [Cerowrt-devel] Just FYI: WNDR3700 (v2???) refurbs available on Amazon for USD49.99 Frank Horowitz
2015-02-26 18:44 ` Dave Taht
2015-02-28  2:07   ` David Lang
2015-02-28  3:27     ` Dave Taht
2015-02-28  4:44       ` David Lang
2015-02-28 15:25         ` [Cerowrt-devel] CeroWrt bits not in OpenWrt (renamed thread) Rich Brown
2015-02-28 16:47           ` Dave Taht
2015-02-28 21:41             ` David Lang
2015-02-28 23:58               ` David Lang
2015-03-12 16:43           ` Rich Brown
2015-03-12 20:31             ` Alan Jenkins
2015-03-12 20:43               ` Alan Jenkins [this message]
2015-03-12 21:21               ` Dave Taht
2015-03-13  0:53                 ` Alan Jenkins
2015-03-13 15:00                   ` Rich Brown
2015-03-12 21:47               ` Toke Høiland-Jørgensen
2015-03-12 21:59                 ` Dave Taht
2015-03-13 15:26                   ` Sebastian Moeller
2015-03-13  0:50                 ` Alan Jenkins
2015-03-13  0:55                   ` Sebastian Moeller
2015-03-13  1:35                 ` David Lang

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=5501FA85.7020107@gmail.com \
    --to=alan.christopher.jenkins@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richb.hanover@gmail.com \
    /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