[Commotion-discuss] Commotion-discuss Digest, Vol 17, Issue 3

Thu Feb 13 18:53:27 UTC 2014

That sounds great.
Poletown Mesh (5 routers on Detroit's East side) is also waiting for
updates.
We are ready to deploy 5 more routers but are waiting for v1.1

thanks for the heads up

tim

On Thu, Feb 13, 2014 at 7:00 AM, <
commotion-discuss-request at lists.chambana.net> wrote:

> Send Commotion-discuss mailing list submissions to
>         commotion-discuss at lists.chambana.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.chambana.net/mailman/listinfo/commotion-discuss
> or, via email, send a message with subject or body 'help' to
>         commotion-discuss-request at lists.chambana.net
>
> You can reach the person managing the list at
>         commotion-discuss-owner at lists.chambana.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Commotion-discuss digest..."
>
>
> Today's Topics:
>
>    1. New Commotion Build? (Anderson Walworth)
>    2. Re: New Commotion Build? (Dan Staples)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 12 Feb 2014 15:23:14 -0500
> From: Anderson Walworth <anderson at alliedmedia.org>
> To: commotion-dev at lists.chambana.net,  commotion-discuss
>         <commotion-discuss at lists.chambana.net>
> Subject: [Commotion-discuss] New Commotion Build?
> Message-ID:
>         <
> CAKenKpL2+keekLxja8LtxutovMRkmD6Z6TrYuVWTBTbZvLDuaA at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Commotion Friends
>
> I tested commotion 1.0 with Andy Gunn when he was in town and we installed
> commotion
> on one Nanostation and one Picostation. After the initial install commotion
> worked well but as soon as one was rebooted they quit meshing with each
> other.
>
> We re-flashed the routers and got the same result the second time as well.
>
> I believe Andy put in a Bug fix request with the developers but I wondered
> if you knew when the next build would be ready to go or if there was a work
> around? We can't deploy the new version if it is broken. I've been
> monitoring the commotion email groups and surprisingly no-one has mentioned
> this issue.
>
> We are also teaching a new batch of digital stewards so I am hoping it
> might get fixed before we get to router flashing part of the curriculum.
>
> Good luck to you all and thanks for all of your help!
>
> Anderson
>
> Allied Media Projects
> Detroit Digital Justice Coalition
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.chambana.net/pipermail/commotion-discuss/attachments/20140212/33684397/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 12 Feb 2014 17:56:08 -0500
> From: Dan Staples <danstaples at opentechinstitute.org>
> To: commotion-discuss at lists.chambana.net,  Commotion Development List
>         <commotion-dev at lists.chambana.net>
> Subject: Re: [Commotion-discuss] New Commotion Build?
> Message-ID: <52FBFC08.1090006 at opentechinstitute.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Anderson,
>
> We also noticed the bug you are talking about, and there was a recent
> code change that should have fixed it. You can see the fix here:
> https://github.com/opentechinstitute/commotiond/pull/82
>
> Andy's bug report is here, and could probably be closed out:
> https://github.com/opentechinstitute/commotion-router/issues/93
>
> Regarding a new version, we are planning to push out version 1.1 by the
> end of the month, which will contain a number of bug fixes. When does
> the flashing section of the Digital Stewards training start?
>
> Thanks for bringing this up!
>
> Dan
>
> On 02/12/2014 03:23 PM, Anderson Walworth wrote:
> > Hi Commotion Friends
> >
> > I tested commotion 1.0 with Andy Gunn when he was in town and we
> > installed commotion
> > on one Nanostation and one Picostation. After the initial install
> > commotion worked well but as soon as one was rebooted they quit meshing
> > with each other.
> >
> > We re-flashed the routers and got the same result the second time as
> well.
> >
> > I believe Andy put in a Bug fix request with the developers but I
> > wondered if you knew when the next build would be ready to go or if
> > there was a work around? We can't deploy the new version if it is
> > broken. I've been monitoring the commotion email groups and surprisingly
> > no-one has mentioned this issue.
> >
> > We are also teaching a new batch of digital stewards so I am hoping it
> > might get fixed before we get to router flashing part of the curriculum.
> >
> > Good luck to you all and thanks for all of your help!
> >
> > Anderson
> >
> > Allied Media Projects
> > Detroit Digital Justice Coalition
> >
> >
> >
> > _______________________________________________
> > Commotion-discuss mailing list
> > Commotion-discuss at lists.chambana.net
> > https://lists.chambana.net/mailman/listinfo/commotion-discuss
> >
>
> --
> Dan Staples
>
> Open Technology Institute
> https://commotionwireless.net
> OpenPGP key: http://disman.tl/pgp.asc
> Fingerprint: 2480 095D 4B16 436F 35AB 7305 F670 74ED BD86 43A9
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Commotion-discuss mailing list
> Commotion-discuss at lists.chambana.net
> https://lists.chambana.net/mailman/listinfo/commotion-discuss
>
>
> ------------------------------
>
> End of Commotion-discuss Digest, Vol 17, Issue 3
> ************************************************
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-discuss/attachments/20140213/c2fa77dc/attachment.html>