mesh documentation

This commit is contained in:
Bob Mottram 2016-08-30 12:10:40 +01:00
parent d022c209a2
commit 8240f189a3
1 changed files with 28 additions and 25 deletions

View File

@ -3,7 +3,7 @@
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!-- 2016-08-30 Tue 11:52 -->
<!-- 2016-08-30 Tue 12:08 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title></title>
@ -252,22 +252,23 @@ for the JavaScript code in this tag.
</div>
<p>
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.
</p>
<div id="outline-container-orgd772d02" class="outline-2">
<h2 id="orgd772d02">Ready made images</h2>
<div class="outline-text-2" id="text-orgd772d02">
</div><div id="outline-container-org3270ae2" class="outline-3">
<h3 id="org3270ae2">Client images</h3>
<div class="outline-text-3" id="text-org3270ae2">
<div id="outline-container-orgce690b1" class="outline-2">
<h2 id="orgce690b1">Ready made images</h2>
<div class="outline-text-2" id="text-orgce690b1">
</div><div id="outline-container-org61d550d" class="outline-3">
<h3 id="org61d550d">Client images</h3>
<div class="outline-text-3" id="text-org61d550d">
<p>
"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).
</p>
<div class="org-src-container">
<pre class="src src-bash">wget https://freedombone.net/downloads/mesh-client-i386.img.xz
<pre class="src 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
sha256sum mesh-client-i386.img.xz
@ -283,11 +284,12 @@ If you're in an emergency and don't have Atheros wifi dongles then there is also
<div class="org-src-container">
<pre class="src src-bash">wget https://freedombone.net/downloads/mesh-client-i386-insecure.img.xz
<pre class="src 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 <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=mesh-client-i386-insecure.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
</pre>
@ -295,19 +297,20 @@ dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">
</div>
</div>
<div id="outline-container-orgec62337" class="outline-3">
<h3 id="orgec62337">Router images</h3>
<div class="outline-text-3" id="text-orgec62337">
<div id="outline-container-org474f6d9" class="outline-3">
<h3 id="org474f6d9">Router images</h3>
<div class="outline-text-3" id="text-org474f6d9">
<p>
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.
</p>
</div>
<div id="outline-container-org1fddd6f" class="outline-4">
<h4 id="org1fddd6f">Beaglebone Black</h4>
<div class="outline-text-4" id="text-org1fddd6f">
<div id="outline-container-org82dc517" class="outline-4">
<h4 id="org82dc517">Beaglebone Black</h4>
<div class="outline-text-4" id="text-org82dc517">
<div class="org-src-container">
<pre class="src src-bash">wget https://freedombone.net/downloads/mesh-router-beaglebone-black.img.xz
<pre class="src 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
sha256sum mesh-router-beaglebone-black.img.xz
@ -321,9 +324,9 @@ dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">
</div>
</div>
<div id="outline-container-orgfb30373" class="outline-2">
<h2 id="orgfb30373">To build the disk image yourself</h2>
<div class="outline-text-2" id="text-orgfb30373">
<div id="outline-container-org1106e17" class="outline-2">
<h2 id="org1106e17">To build the disk image yourself</h2>
<div class="outline-text-2" id="text-org1106e17">
<p>
It's better not to trust images downloaded from random places on the interwebs. Chances are that unless you are in the web of trust of the above GPG signatures then they don't mean very much to you. If you actually want something trustworthy then build the images from scratch. It will take some time. Here's how to do it.
</p>
@ -424,9 +427,9 @@ This site can also be accessed via a Tor browser at <a href="http://4fvfozz6g3zm
</div>
</div>
<div id="outline-container-org4311dfe" class="outline-2">
<h2 id="org4311dfe">How to use it</h2>
<div class="outline-text-2" id="text-org4311dfe">
<div id="outline-container-orgd1f0320" class="outline-2">
<h2 id="orgd1f0320">How to use it</h2>
<div class="outline-text-2" id="text-orgd1f0320">
<p>
When you first boot from the USB drive the system will create some encryption keys, assign a unique network address to the system and then reboot itself. When that's done you should see a prompt asking for a username. This username just makes it easy for others to initially find you on the mesh and will appear in the list of users.
</p>