[Interop-dev] common manageable firmware

Fri Apr 13 00:14:46 CEST 2012

In Pisa we are using a third approach, at compile time we just put in
the node a simple scripts that at first/second boot gather data about
the node ( interfaces, mac address ecc ecc ) and auto-configure it for
meshing, after that there is a small uci file with the more important
things you can need to change after the node is mounted,

so you can use the same image for all nodes without recompiling


to achieve that the scripts set an ipv6 to make reachable the node
knowing from compile time only the prefix and than it add an ip to the
reacheable interface done by prefix+mac address of eth0 (that is just an
example of how we solved a problem but we ca make that different )

I think the more flexible solution possible is a combination of the 3
approach

> suggestion is: we should combine our efforts also on this.
I completely agree with that

On 04/12/12 23:57, Mitar wrote:
>> I am trying to do an openwrt based firmware, usable by all the
>> communities, so it will be more flexible that the actual firmware we
>> have on ours communities.
> 
> I think there are two approaches here communities are taking:
> 
> - static/same firmware you apply to nodes and then do manual or
> automatic on top of it once they are connected to the network
> - generated firmware for one specific node with configuration in some
> way "baked in"
> 
> There is one proposal for this year's GSoC from Freifunk community for
> improving the second approach. In the sense of building a more
> customizable official OpenWrt image builder + web interface.
> 
> (We are using also the second approach in wlan slovenija, but with our
> own image generator combined with our node database.)
> 
> So the first approach is not familiar to me. But it could be maybe
> interesting to combine them? Like to have first approach a failback for
> the second one?
> 
> Anyway, the best would be to push this into OpenWrt together with that
> new image builder system? Maybe this could be just one option for that
> image builder system? Like an "auto-configuring" node? So my only
> suggestion is: we should combine our efforts also on this.
> 
> 
> Mitar
> Delivered-To: (spam-protected)
> Received: by 10.204.57.131 with SMTP id c3csp264298bkh;
>         Thu, 12 Apr 2012 14:58:01 -0700 (PDT)
> Received: by 10.180.104.65 with SMTP id gc1mr9388046wib.13.1334267881419;
>         Thu, 12 Apr 2012 14:58:01 -0700 (PDT)
> Return-Path: <(spam-protected)>
> Received: from mail2.ninux.org (static.242.245.47.78.clients.your-server.de. [78.47.245.242])
>         by mx.google.com with ESMTP id m34si7513369weq.86.2012.04.12.14.58.00;
>         Thu, 12 Apr 2012 14:58:01 -0700 (PDT)
> Received-SPF: neutral (google.com: 78.47.245.242 is neither permitted nor denied by domain of (spam-protected)) client-ip=78.47.245.242;
> Authentication-Results: mx.google.com; spf=neutral (google.com: 78.47.245.242 is neither permitted nor denied by domain of (spam-protected)) smtp.mail=(spam-protected); dkim=pass header.i=@gmail.com
> Received: from mail.ninux.org (unknown [176.62.53.1])
> 	by mail2.ninux.org (Postfix) with ESMTP id 78C5FC07ED;
> 	Thu, 12 Apr 2012 21:58:02 +0000 (UTC)
> Received: by mail.ninux.org (Postfix)
> 	id 666F71CC00F; Thu, 12 Apr 2012 21:57:28 +0000 (UTC)
> Delivered-To: (spam-protected)
> Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43])
> 	by mail.ninux.org (Postfix) with ESMTPS id 4D981205FF
> 	for <(spam-protected)>; Thu, 12 Apr 2012 21:57:24 +0000 (UTC)
> Received: by wgbdr12 with SMTP id dr12so1994861wgb.12
>         for <(spam-protected)>; Thu, 12 Apr 2012 14:57:56 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>         d=gmail.com; s=20120113;
>         h=mime-version:date:message-id:subject:from:to:cc:content-type
>          :content-transfer-encoding;
>         bh=GcoWvnxlva7V5s53jJe7Nbw4FjYn7ZAc/CwKi9Pbork=;
>         b=e1YiGatvmFfHSyVcs/YVxvlr9hDiKHyMV46XX7SlQHdxwhPH9oZLIVnvDLE4u94mu9
>          ZLDihRClOO8HZp6KsVFOb0wBtqg08MlfZVuKd0aRDNZnD26f2xPbb8Vo41hfPN3kR9Vi
>          IfrIvY1X606DBJ1LSfkwBNBa4LeHHHye3sgMTYkknsvy54pDZkRS45dwWhToKcphhWjP
>          7YzN3ag2OS+I7Uu17l+b//HP9WRdss+Y6d9HOgCe9M4YqO6/dJfONtx6MRbHvWf39Ypv
>          SgDCd7qRuqFOxAIPnY4etbowL/HFK1SgUzSmJ+FEgieTz9eMSiDoLR/tkRaOPWiA7CKf
>          tx1w==
> MIME-Version: 1.0
> Received: by 10.180.88.67 with SMTP id be3mr9299435wib.20.1334267875898; Thu,
>  12 Apr 2012 14:57:55 -0700 (PDT)
> Received: by 10.180.93.195 with HTTP; Thu, 12 Apr 2012 14:57:55 -0700 (PDT)
> Date: Thu, 12 Apr 2012 23:57:55 +0200
> Message-ID: <(spam-protected)>
> Subject: Nerds di Ninux alla SNIA
> From: "ZioPRoTo (Saverio Proto)" <(spam-protected)>
> To: nisotom <(spam-protected)>, carlo tagliaferri <(spam-protected)>, 
> 	pieropierino di silvestro <(spam-protected)>, Marco Salerosso <(spam-protected)>
> Cc: contatti <(spam-protected)>
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> 
> Hello,
> 
> qui zioproto dal mondo Ninux.
> 
> come forse gi=C3=A0 sapete Fusolab si sposta. Abbiamo lasciato il piccolo
> locale in affitto a Via G. Pitacco per spostarci in una nuovo posto
> pi=C3=B9 grande all'alessandrino.
> 
> il trasloco non =C3=A8 indolore, e per un paio di Giovedi non abbiamo un
> posto dove riunirci.
> 
> Ninux fa l'assemblea settimanale il Giovedi sera dalle 21:00. L'orario
> di chiusura al Fusolab era molto elastico, ma possiamo finire per
> mezzanotte se necessario.
> 
> I nerds chiedono se =C3=A8 possibile per giovedi 19 e giovedi 26 aprile
> fare la riunione di Ninux alla SNIA. Siamo circa dalle 30 alle 40
> persone di solito.
> 
> fatemi sapere se =C3=A8 una cosa possibile, grazie !
> 
> Saverio