Re: [Cerowrt-devel] [Commotion-dev] Commotion Router v1.2 enters release testing

Re: [Cerowrt-devel] [Commotion-dev] Commotion Router v1.2 enters release testing

[Dave Taht]

[-- Attachment #1: Type: text/plain, Size: 3909 bytes --]

my hope is that you are also including the sqm-scripts or something similar
with this release?

We have it in chaos calmer, I am not sure if the backport made it to
barrier breaker yet.

I've always viewed one of the biggest problems with sharing bandwidth as
sharing it well.

http://snapon.lab.bufferbloat.net/~cero2/jimreisert/results.html


On Fri, Mar 27, 2015 at 6:36 PM, Josh King <jking@opentechinstitute.org>
wrote:

> Hi all,
>
> We've just entered release testing for our v1.2 release of Commotion
> Router! We have testing images available below:
>
> https://downloads.commotionwireless.net/router/1.2rc1/
>
> The v1.2 release will include the following new features:
> * Upgraded to OpenWRT Barrier Breaker as a base, providing better
> performance, additional router support, and many other improvements.
> * The nodogsplash splash screen has been replaced with a fork of
> luci_splash, allowing for less resource usage.
> * The addition of the new commotion-dnsproxy means that the splash
> screen will work even when there is no internet gateway available.
> * Better support for different wifi countrycodes and radios that support
> more than one band.
> * v2.0 of Commotion Service Manager, for better reliability and less
> resource usage.
> * A new upgrade utility, that provides for forward compatibility and
> signed images.
> * Built with a new buildsystem that makes it easier to support multiple
> hardware platforms and build images more quickly and consistently.
> * Numerous bugfixes and upgrades.
>
> If you're interested in helping with testing, just let us know! More
> hands make the testing process go quickly (hopefully everything will go
> great and we can release next week!). We have a fairly thorough testing
> protocol that you can use, which we've been using since early stages of
> the previous release:
>
>
> https://drive.google.com/drive/u/0/#folders/0B38UMlgDzTMPfk9JWDFKUGE1UFZTVGtHQzJtOV8wWVUtWTAtNTloYkxwSTh3UmxfSkt6SDQ
>
> There are a few things to be aware of with these images:
> * The new images for the upgrade utility of the extension '.bundle', but
> they can also be used in previous versions of Commotion without any
> problems. These can not be used for flashing a router from stock
> firmware, which is why we also still provide 'factory.bin' images.
> * Even though the new upgrade utility has the capability for signing
> images, these images are not signed. Final v1.2 release images will be
> signed.
> * These images do not yet contain upgrade scripts for the new splash
> screen. If you upgrade an existing Commotion install while saving
> settings and the splash screen doesn't work, please try reflashing
> without saving settings reporting that the splash screen doesn't work.
> * During development, we experienced an intermittent issue with Barrier
> Breaker being more sensitive to low memory conditions, triggering the
> out of memory killer and rebooting the node. If your node reboots during
> testing, you may be running into this issue. We figure more testers and
> more data will help us track it down if it's still a problem.
>
> Anyway, if you want to help with testing, please try out the images and
> let us know how it goes. Otherwise, we'll be releasing final, stable and
> supported v1.2 images as soon as we conclude with testing. Thanks!
>
> --
> Josh King
> Lead Technologist
> The Open Technology Institute
> http://opentechinstitute.org
> PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999
>
>
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev@lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-dev
>
>


-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

[-- Attachment #2: Type: text/html, Size: 5172 bytes --]

Re: [Cerowrt-devel] [Commotion-dev] Commotion Router v1.2 enters release testing

[Josh King]

[-- Attachment #1: Type: text/plain, Size: 4899 bytes --]

Hi Dave,

I do not think it's in Barrier Breaker, but I would be happy to add it
to our repository so that people can install it on Commotion if they wish.

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.

On 03/27/2015 09:48 PM, Dave Taht wrote:
> my hope is that you are also including the sqm-scripts or something
> similar with this release?
> 
> We have it in chaos calmer, I am not sure if the backport made it to
> barrier breaker yet.
> 
> I've always viewed one of the biggest problems with sharing bandwidth as
> sharing it well.
> 
> http://snapon.lab.bufferbloat.net/~cero2/jimreisert/results.html
> 
> 
> On Fri, Mar 27, 2015 at 6:36 PM, Josh King <jking@opentechinstitute.org
> <mailto:jking@opentechinstitute.org>> wrote:
> 
>     Hi all,
> 
>     We've just entered release testing for our v1.2 release of Commotion
>     Router! We have testing images available below:
> 
>     https://downloads.commotionwireless.net/router/1.2rc1/
> 
>     The v1.2 release will include the following new features:
>     * Upgraded to OpenWRT Barrier Breaker as a base, providing better
>     performance, additional router support, and many other improvements.
>     * The nodogsplash splash screen has been replaced with a fork of
>     luci_splash, allowing for less resource usage.
>     * The addition of the new commotion-dnsproxy means that the splash
>     screen will work even when there is no internet gateway available.
>     * Better support for different wifi countrycodes and radios that support
>     more than one band.
>     * v2.0 of Commotion Service Manager, for better reliability and less
>     resource usage.
>     * A new upgrade utility, that provides for forward compatibility and
>     signed images.
>     * Built with a new buildsystem that makes it easier to support multiple
>     hardware platforms and build images more quickly and consistently.
>     * Numerous bugfixes and upgrades.
> 
>     If you're interested in helping with testing, just let us know! More
>     hands make the testing process go quickly (hopefully everything will go
>     great and we can release next week!). We have a fairly thorough testing
>     protocol that you can use, which we've been using since early stages of
>     the previous release:
> 
>     https://drive.google.com/drive/u/0/#folders/0B38UMlgDzTMPfk9JWDFKUGE1UFZTVGtHQzJtOV8wWVUtWTAtNTloYkxwSTh3UmxfSkt6SDQ
> 
>     There are a few things to be aware of with these images:
>     * The new images for the upgrade utility of the extension '.bundle', but
>     they can also be used in previous versions of Commotion without any
>     problems. These can not be used for flashing a router from stock
>     firmware, which is why we also still provide 'factory.bin' images.
>     * Even though the new upgrade utility has the capability for signing
>     images, these images are not signed. Final v1.2 release images will be
>     signed.
>     * These images do not yet contain upgrade scripts for the new splash
>     screen. If you upgrade an existing Commotion install while saving
>     settings and the splash screen doesn't work, please try reflashing
>     without saving settings reporting that the splash screen doesn't work.
>     * During development, we experienced an intermittent issue with Barrier
>     Breaker being more sensitive to low memory conditions, triggering the
>     out of memory killer and rebooting the node. If your node reboots during
>     testing, you may be running into this issue. We figure more testers and
>     more data will help us track it down if it's still a problem.
> 
>     Anyway, if you want to help with testing, please try out the images and
>     let us know how it goes. Otherwise, we'll be releasing final, stable and
>     supported v1.2 images as soon as we conclude with testing. Thanks!
> 
>     --
>     Josh King
>     Lead Technologist
>     The Open Technology Institute
>     http://opentechinstitute.org
>     PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999
> 
> 
>     _______________________________________________
>     Commotion-dev mailing list
>     Commotion-dev@lists.chambana.net
>     <mailto:Commotion-dev@lists.chambana.net>
>     https://lists.chambana.net/mailman/listinfo/commotion-dev
> 
> 
> 
> 
> -- 
> Dave Täht
> Let's make wifi fast, less jittery and reliable again!
> 
> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

-- 
Josh King
Lead Technologist
The Open Technology Institute
http://opentechinstitute.org
PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [Cerowrt-devel] [Commotion-dev] Commotion Router v1.2 enters release testing

[Jonathan Morton]

> 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