<div dir="ltr"><div>Thank you Adam for sharing instructions for building mesh infrastructure off of stock OpenWRT. It is unfortunately very difficult for the mesh-oriented derivatives of OpenWRT to gain staying power (Commotion Wireless by far not being the first such to become a tad stale). So, staying close to stock OpenWRT has benefits.<br><br>WasabiNet, for example, started out using ROBIN mesh firmware, based on
OpenWRT Backfire, and many aspects of that obsolete firmware still
linger on in ugly Frankenstein form. Nowadays, I also basically compile off current OpenWRT trees, likely to the point of being interoperable with MetaMesh nodes.<br><br></div>One key missing ingredient I'd like to point thread participants to is a control and monitoring dashboard. CW didn't quite have the opportunity yet to deploy one, but I have been watching the progress of Nodewatcher from WLAN Slovenia pretty closely. Indeed, I was able to compile its client on OpenWRT BB for testing. I was very impressed with it, although I didn't get a chance to test drive its dashboard thoroughly.<br><br>The precise firmware makeup used by different community mesh groups will vary (i.e. varying degrees of distance from stock OpenWRT), but the prospect of sharing a monitoring and dashboard solution could help focus energies, since all large meshes need that. Nodewatcher looks robust and thorough enough to be useful to many parties.<br><br>You can read more about Nodewatcher here:<br><a href="https://dev.wlan-si.net/wiki/Nodewatcher" target="_blank">https://dev.wlan-si.net/wiki/Nodewatcher</a><br><br><div><br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 4, 2016 at 3:56 PM, Marina Brown <span dir="ltr"><<a href="mailto:catskillmarina@gmail.com" target="_blank">catskillmarina@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 05/04/2016 02:53 PM, Adam Longwill wrote:<br>
> Meta Mesh in Pittsburgh has begun developing a working system compatible<br>
> with Commotion (we use OLSR that grew from using Commotion) running<br>
> stock OpenWRT.<br>
><br>
> You can find our instructions on our<br>
> website: <a href="http://www.metamesh.org/#!how-to-configure-a-router/b7luv" rel="noreferrer" target="_blank">http://www.metamesh.org/#!how-to-configure-a-router/b7luv</a><br>
><br>
<br>
> And we will be shipping pre-built indoor and outdoor routers using 2.4<br>
> GHz as soon as we finish manufacturing the cases at www.metamesh.tech<br>
</span>> <<a href="http://www.metamesh.tech" rel="noreferrer" target="_blank">http://www.metamesh.tech</a>>.<br>
><br>
<br>
Thanks a lot !<br>
<br>
<br>
-- Marina Brown<br>
<span><br>
<br>
> Feel free to join our IRC channel on Freenode at #PittMesh if you have<br>
> any further questions.<br>
><br>
> Adam<br>
><br>
> On Wed, May 4, 2016 at 2:49 PM, <<a href="mailto:dpeel@vtlink.net" target="_blank">dpeel@vtlink.net</a><br>
</span><span>> <mailto:<a href="mailto:dpeel@vtlink.net" target="_blank">dpeel@vtlink.net</a>>> wrote:<br>
><br>
> If we find we can't put Commotion on new versions of Ubiquiti<br>
> routers, what would be our best strategy? Is Commotion updating the<br>
> firmware to work on newer versions? How about Commotion for other<br>
> routers? Commotion on Raspberry Pie? We need suggestions as we are<br>
> going to quite a lot of effort to become a non-profit to provide<br>
> community supported mesh internet to our low income neighborhood. We<br>
> have had a pilot project for about a year using Ubiquiti routers.<br>
><br>
><br>
> _______________________________________________<br>
> Commotion-discuss mailing list<br>
> <a href="mailto:Commotion-discuss@lists.chambana.net" target="_blank">Commotion-discuss@lists.chambana.net</a><br>
</span>> <mailto:<a href="mailto:Commotion-discuss@lists.chambana.net" target="_blank">Commotion-discuss@lists.chambana.net</a>><br>
> <a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
<div><div>><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Commotion-discuss mailing list<br>
> <a href="mailto:Commotion-discuss@lists.chambana.net" target="_blank">Commotion-discuss@lists.chambana.net</a><br>
> <a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
><br>
<br>
<br>
</div></div><br>_______________________________________________<br>
Commotion-discuss mailing list<br>
<a href="mailto:Commotion-discuss@lists.chambana.net" target="_blank">Commotion-discuss@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>314-246-9434<br></div></div>
</div></div>