Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Josh King <jking@opentechinstitute.org>
Cc: Commotion Development List <commotion-dev@lists.chambana.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Commotion-dev] Commotion Router v1.2 enters release testing
Date: Sat, 28 Mar 2015 04:24:36 +0200	[thread overview]
Message-ID: <80119C6B-CB14-4CEF-94A8-459087DBD2AD@gmail.com> (raw)
In-Reply-To: <55160C84.6070808@opentechinstitute.org>


> On 28 Mar, 2015, at 04:05, Josh King <jking@opentechinstitute.org> wrote:
> 
> I think the biggest problem we've had with including traffic shaping by
> default in our images is figuring out how best to provide an interface
> to users that is easy to understand and utilize. Any suggestions or help
> in that regard would be welcome.

Most people don’t have the first clue about it, or even that it is a necessary or desirable thing.  So ideally, you need something with either no knobs that’s invisible (or has a simple checkbox to turn it on with), or something with as few knobs as possible and clear instructions on how to turn them.

I’m currently working on something along those lines.

The one parameter that’s definitely situation-dependent is the bandwidth to shape at.  If you have an integrated DSL modem, you can probably derive that number from querying the sync rate.  If you don’t, you’ll have to ask the user to set it.  Even if you can detect a sync rate, though, you should let the user override it - some DSL ISPs throttle the connection by other means than sync rate.  NB: DSL sync rates do change occasionally, so poll it every minute and use “tc qdisc change…” to adjust without spilling the existing queues.

For everything else, put in sensible defaults, calculating from the given shaping rate where necessary, and do your best to avoid bothering the user with details up front.  At the same time, it’s probably wise to provide a way to see what’s being done behind the scenes, but make that an extra click.

If you want to also put in an advanced mode for people who do know what they’re doing, you can, but hide it behind an “advanced, here be dragons” button and make it easy to go back to the sane defaults.

 - Jonathan Morton


      reply	other threads:[~2015-03-28  2:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5516059A.8080503@opentechinstitute.org>
2015-03-28  1:48 ` Dave Taht
2015-03-28  2:05   ` Josh King
2015-03-28  2:24     ` Jonathan Morton [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=80119C6B-CB14-4CEF-94A8-459087DBD2AD@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=commotion-dev@lists.chambana.net \
    --cc=jking@opentechinstitute.org \
    /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