[Battlemesh] LibreRouter

Pau pau at dabax.net
Thu Dec 15 20:14:55 CET 2016

On 15/12/16 19:33, Henning Rogge wrote:
> Just to say it,
> if we can we should use the same hardware as last year, because two
> Wifi interfaces one, dedicated ethernet plug and one 4-port switch we
> can (VLAN) configure 3/1 is really good for experimentation.
> Henning

Hi Henning, take a look on the specs of librerouter [1].

Is not yet the final version (we are now discussing about using AR9558
instead of AR9344) but we will have three radios plus multiple ethernet


[1] https://librerouter.org/document/specifications-sheet-v5/

> On Thu, Dec 15, 2016 at 6:52 PM, Gui Iribarren <gui at altermundi.net> wrote:
>> On 15/12/16 18:37, willi uebelherr wrote:
>>> On 15/12/2016 07:24, Gui Iribarren wrote:
>>>> ...
>>>> I'm thinking out loud, that maybe with the librerouter we could set
>>>> something up, when we have deployed them in the real networks. We'll
>>>> have double-flash space, so we can put two firmwares (originally
>>>> intended for safe sysupgrading, but could be used for "testbed" and
>>>> "production" firmwares). Combining that with the hardware watchdog...
>>>> Anyway, will come back to this idea in a few months when we have the
>>>> prototypes.
>>> Dear Gui and all,
>>> i searched for LibreRouter.
>>> Librerouter/Librekernel
>>> https://github.com/Librerouter/Librekernel
>> totally unrelated
>>> LibreRouter
>>> https://www.f6s.com/librerouter
>> totally unrelated as well
>>> Open Router
>>> http://programafrida.net/en/archivos/project/router-libre
>>> LibreRouter project awarded FRIDA 2016 scale-up grant
>>> https://blog.altermundi.net/article/el-proyecto-librerouter-premios-frida/
>> these two are correct
>> as well as https://librerouter.org/
>> sorry for the confusion
>> re: benjamin regarding watchdog,
>> it's a PIC that every 5 minutes decides to reboot the board or not. If
>> it received a "ping" from userspace (simple bit up, bit down through a
>> gpio), it won't reboot. Then, there's a very simple script running in
>> userspace, sending that ping every 2 minutes for example. In case of a
>> kernel panic or similar, the watchdog will not get pinged and will
>> reboot the node.
>> There's already the userspace software in available in openwrt, thanks
>> to the implementation of such a watchdog in Open-Mesh routers.
>> cheers!
>>> It seems to me a big confusion. I agree and understand to develop the
>>> router hardware itself. But from my experience in Latin America, also in
>>> Argentina, never i have found a real strong process for hw-development.
>>> And in Github Librerouter/Librekernel we find a large collection of
>>> anything. But the task for a router is to route the packets through.
>>> Therefore, the fisrst question is, based on what information we can
>>> route. then, we can ask us, what hardware we need.
>>> And the routers in our environment act mostly with radio
>>> interconnection. But here we can abstract from the concrete transmission
>>> technology and use a bidirectional connection to the transmitter device.
>>> For cable connection we can use it directly.
>>> This means, that in our space also the transmission technology stay in
>>> the center. And i think, there we have the biggest challenges. because
>>> if we look in the community networks reality, the lack of net-structure
>>> is the biggest lack for community networks.
>>> I don't understand this project.
>>> many greetings, willi
>>> Asuncion, Paraguay
>>> _______________________________________________
>>> Battlemesh mailing list
>>> Battlemesh at ml.ninux.org
>>> http://ml.ninux.org/mailman/listinfo/battlemesh
>> _______________________________________________
>> Battlemesh mailing list
>> Battlemesh at ml.ninux.org
>> http://ml.ninux.org/mailman/listinfo/battlemesh
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20161215/f82b8244/attachment-0001.sig>

More information about the Battlemesh mailing list