<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Thanks :-)<br>
<br>
I suggested a friend to take a look at nodewatcher-agent because
he needed something similar.<br>
<br>
Federico<br>
<br>
<br>
<br>
On 02/24/2015 10:20 AM, Jernej Kos wrote:<br>
</div>
<blockquote cite="mid:54EC4278.9080609@kos.mx" type="cite">
<pre wrap="">Hello!
Wireless-info should really not be used anymore. I am not sure why Mitar
posted this link, but we are now using nodewatcher-agent (or more
specifically its wireless module) which uses libiwinfo to obtain all the
wireless data.
Netmeasured is a small application that performs periodic pings between
two nodes and reports loss statistics via ubus. It is currently used for
some simple KORUZA measurements.
Jernej
On 24. 02. 2015 10:17, Nemesis wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Thanks for sharing.
Could you expand a bit more on the wireless-info and netmeasured repos?
Federico
On 02/23/2015 07:39 PM, Mitar wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi!
Just wanting to share some new stuff we have been using in wlan
slovenija network.
So for managing our servers, we started using Salt and Docker. You can
find our Salt configurations here:
<a class="moz-txt-link-freetext" href="https://github.com/wlanslovenija/servers-salt-states">https://github.com/wlanslovenija/servers-salt-states</a>
<a class="moz-txt-link-freetext" href="https://github.com/tozd/salt">https://github.com/tozd/salt</a>
We are putting all stuff into Docker images. Like nodewatcher, routing, etc.
<a class="moz-txt-link-freetext" href="https://github.com/wlanslovenija/docker-router-olsrd">https://github.com/wlanslovenija/docker-router-olsrd</a>
And interesting thing we started doing is putting OpenWrt firmware
generators for each platform into its own Docker image:
<a class="moz-txt-link-freetext" href="https://github.com/wlanslovenija/firmware-core">https://github.com/wlanslovenija/firmware-core</a>
In this way it is easy to share already compiled firmware generators.
People do not have to compile them themselves. You can then simply SSH
into it and compile images for that platform. (We use nodewatcher to
connect to them and compile based on the set of packages our users want
and with configuration baked in into the image itself.)
For gateways and VPN servers, we are simply using (or planing to use)
OpenWrt images generated by nodewatcher. :-) For x86 platform and it
works. In this way it is easy to reuse the existing stack. The servers
above are mostly for website, nodewatcher itself, etc.
We have also quite few OpenWrt packages:
<a class="moz-txt-link-freetext" href="https://github.com/wlanslovenija/firmware-packages-opkg">https://github.com/wlanslovenija/firmware-packages-opkg</a>
So for OpenWrt we are trying to put everything into packages. For
servers into Docker images.
For configuring the network stack for Docker we are using:
<a class="moz-txt-link-freetext" href="https://github.com/wlanslovenija/netcfg">https://github.com/wlanslovenija/netcfg</a>
Some random apps we created:
<a class="moz-txt-link-freetext" href="https://github.com/wlanslovenija/wireless-info">https://github.com/wlanslovenija/wireless-info</a>
<a class="moz-txt-link-freetext" href="https://github.com/wlanslovenija/netmeasured">https://github.com/wlanslovenija/netmeasured</a>
I am sharing all this stuff so that others see if there is anything
interesting so that we do not duplicate too much things. Or that we
might use the same patterns/tools to be easier to reuse. Like Salt,
Docker. The most interesting for me is that if we would agree upon a
simple format for generator images, it would be a great way to share
firmware builders one can simply plug into their own systems. We all use
OpenWrt based stuff, this is then just to make module around it so that
I can ship to somebody a firmware they are not used to, but they can
still generate it with tools they are used to.
Mitar
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Interop-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Interop-dev@lists.funkfeuer.at">Interop-dev@lists.funkfeuer.at</a>
<a class="moz-txt-link-freetext" href="https://lists.funkfeuer.at/mailman/listinfo/interop-dev">https://lists.funkfeuer.at/mailman/listinfo/interop-dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Interop-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Interop-dev@lists.funkfeuer.at">Interop-dev@lists.funkfeuer.at</a>
<a class="moz-txt-link-freetext" href="https://lists.funkfeuer.at/mailman/listinfo/interop-dev">https://lists.funkfeuer.at/mailman/listinfo/interop-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>