-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/20/2012 04:16 PM, Markus Sabadello wrote:
I've been told though that olsr is still the way to go for large
networks.
Kind of. If the mesh nodes pushing the packets have a fair amount of
RAM olsrd is okay. The thing about that particular
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/20/2012 10:12 AM, Dave Taht wrote:
There are plenty of mesh protocols available - 802.11s, batman,
olsr, and my own fav babel. 802.11s operates at layer 2, is limited
to 32
There are over 70 mesh routing protocols; not all of them have been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/20/2012 02:13 PM, John Gilmore wrote:
Internet while the problem is happening, to debug it. Many, many
OLPC mesh problems occurred in the field which could not be
replicated in the lab, which made them 10x or 100x harder to fix.
This meant
I'm having a hard time wrapping my head around the security implications
of this discussion.
I think that's in part because goals like
censorship-resistant-connectivity and privacy seem in conflict.
To the best of my understanding these routing protocols have not been
designed with the goal of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sam,
I am one of the developers of Project Byzantium and heard about this
discussion from The Doctor. Freedombox is not our project so we have no
authority to direct which way the project goes, but we have done some
significant research and
On Wed, 20 Jun 2012 22:16:32 -0400 (EDT), bnewb...@robocracy.org wrote:
General purpose Configuration Management seems to be a crucial component
of the FreedomBox software stack/distribution. It needs to be secure,
accessible (elegant user experience for diverse userbase), reliable,
