From d022c209a2a42582f60f7d366d359b8672e27898 Mon Sep 17 00:00:00 2001 From: Bob Mottram Date: Tue, 30 Aug 2016 12:08:23 +0100 Subject: [PATCH] mesh documentation --- doc/EN/mesh.org | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/EN/mesh.org b/doc/EN/mesh.org index 14f0ae63..71324f6c 100644 --- a/doc/EN/mesh.org +++ b/doc/EN/mesh.org @@ -18,13 +18,14 @@ [[file:images/mesh_screenshot.jpg]] #+END_CENTER -Mesh networks are useful as a quick way to make a fully decentralised communications system which is not connected to the internet. Think festivals, hacker conferences, onboard ships at sea, disaster/war zones, small business internal office communications, protests, remote areas of the world, scientific expeditions and off-world space colonies. All the cool stuff. The down side is that you can't access any internet content. The upside is that you can securely communicate with anyone on the local mesh. No ISPs. No payments or subscriptions beyond the cost of obtaining the hardware. Systems need to be within wifi range of each other for the mesh to be created. It can be an ultra-convenient way to do purely local communications. +Mesh networks are useful as a quick way to make a fully decentralised communications system which is not connected to or reliant upon the internet. Think festivals, hacker conferences, onboard ships at sea, disaster/war zones, small business internal office communications, protests, remote areas of the world, scientific expeditions and off-world space colonies. All the cool stuff. The down side is that you can't access any internet content. The upside is that you can securely communicate with anyone on the local mesh. No ISPs. No payments or subscriptions beyond the cost of obtaining the hardware. Systems need to be within wifi range of each other for the mesh to be created. It can be an ultra-convenient way to do purely local communications. * Ready made images ** Client images -"Client" isn't exactly the right term, but it's a mesh peer with a user interface. These images can be copied to a USB drive, then you can plug it into a laptop/netbook/desktop machine and boot from it. You will probably also need an Atheros USB wifi dongle, because most built-in wifi usually requires proprietary firmware. +"Client" isn't exactly the right term, but it's a mesh peer with a user interface. These images can be copied to a USB drive, then you can plug it into a laptop/netbook/desktop machine and boot from it. You will probably also need an Atheros USB wifi dongle, because most built-in wifi usually requires proprietary firmware. In the commands below substitute /dev/sdX with the USB drive device, excluding any trailing numbers (eg. /dev/sdb). #+begin_src bash +sudo apt-get install xz-utils wget wget https://freedombone.net/downloads/mesh-client-i386.img.xz wget https://freedombone.net/downloads/mesh-client-i386.img.xz.sig gpg --verify mesh-client-i386.img.xz.sig @@ -37,11 +38,12 @@ dd bs=1M if=mesh-client-i386.img of=/dev/sdX conv=fdatasync If you're in an emergency and don't have Atheros wifi dongles then there is also an "insecure" image which contains some proprietary wifi drivers which may work with a wider range of laptops. Proprietary drivers *are not recommended* because they're unsupportable and may be exploitable or contain malicious antifeatures which fundamentally compromise the security of the network. However, the trade-off between security/maintainability and simply having the ability to communicate at all may be a valid one in some situations. #+begin_src bash +sudo apt-get install xz-utils wget wget https://freedombone.net/downloads/mesh-client-i386-insecure.img.xz wget https://freedombone.net/downloads/mesh-client-i386-insecure.img.xz.sig gpg --verify mesh-client-i386-insecure.img.xz.sig sha256sum mesh-client-i386-insecure.img.xz - +2aa1552d695485505b6a145857e5cebb7dc365dbf9614488f474bf5ac1149473 unxz mesh-client-i386-insecure.img.xz dd bs=1M if=mesh-client-i386-insecure.img of=/dev/sdX conv=fdatasync #+end_src @@ -50,6 +52,7 @@ dd bs=1M if=mesh-client-i386-insecure.img of=/dev/sdX conv=fdatasync Routers are intended to build network coverage for an area using small and low cost hardware. You can bolt them to walls or leave them on window ledges. They don't have any user interface and their only job is to move network traffic across the mesh. Copy the image to a microSD card and insert it into the router, plug in an Atheros wifi dongle and power on. That should be all you need to do. *** Beaglebone Black #+begin_src bash +sudo apt-get install xz-utils wget wget https://freedombone.net/downloads/mesh-router-beaglebone-black.img.xz wget https://freedombone.net/downloads/mesh-router-beaglebone-black.img.xz.sig gpg --verify mesh-router-beaglebone-black.img.xz.sig