|
|
@@ -3,7 +3,7 @@
|
|
3
|
3
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
4
|
4
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
|
5
|
5
|
<head>
|
|
6
|
|
-<!-- 2016-08-30 Tue 12:26 -->
|
|
|
6
|
+<!-- 2016-08-30 Tue 13:04 -->
|
|
7
|
7
|
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
|
8
|
8
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
9
|
9
|
<title></title>
|
|
|
@@ -255,12 +255,12 @@ for the JavaScript code in this tag.
|
|
255
|
255
|
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.
|
|
256
|
256
|
</p>
|
|
257
|
257
|
|
|
258
|
|
-<div id="outline-container-orge45c964" class="outline-2">
|
|
259
|
|
-<h2 id="orge45c964">Ready made images</h2>
|
|
260
|
|
-<div class="outline-text-2" id="text-orge45c964">
|
|
261
|
|
-</div><div id="outline-container-org3985b84" class="outline-3">
|
|
262
|
|
-<h3 id="org3985b84">Client images</h3>
|
|
263
|
|
-<div class="outline-text-3" id="text-org3985b84">
|
|
|
258
|
+<div id="outline-container-org6c42146" class="outline-2">
|
|
|
259
|
+<h2 id="org6c42146">Ready made images</h2>
|
|
|
260
|
+<div class="outline-text-2" id="text-org6c42146">
|
|
|
261
|
+</div><div id="outline-container-org23d3e1e" class="outline-3">
|
|
|
262
|
+<h3 id="org23d3e1e">Client images</h3>
|
|
|
263
|
+<div class="outline-text-3" id="text-org23d3e1e">
|
|
264
|
264
|
<p>
|
|
265
|
265
|
"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).
|
|
266
|
266
|
</p>
|
|
|
@@ -279,6 +279,10 @@ sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-n
|
|
279
|
279
|
</div>
|
|
280
|
280
|
|
|
281
|
281
|
<p>
|
|
|
282
|
+To get a number of systems onto the mesh repeat the <i>dd</i> command to create however many bootable USB drives you need.
|
|
|
283
|
+</p>
|
|
|
284
|
+
|
|
|
285
|
+<p>
|
|
282
|
286
|
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 <b>are not recommended</b> 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.
|
|
283
|
287
|
</p>
|
|
284
|
288
|
|
|
|
@@ -297,16 +301,16 @@ sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-n
|
|
297
|
301
|
</div>
|
|
298
|
302
|
</div>
|
|
299
|
303
|
|
|
300
|
|
-<div id="outline-container-orgd78876a" class="outline-3">
|
|
301
|
|
-<h3 id="orgd78876a">Router images</h3>
|
|
302
|
|
-<div class="outline-text-3" id="text-orgd78876a">
|
|
|
304
|
+<div id="outline-container-orgcb6db0b" class="outline-3">
|
|
|
305
|
+<h3 id="orgcb6db0b">Router images</h3>
|
|
|
306
|
+<div class="outline-text-3" id="text-orgcb6db0b">
|
|
303
|
307
|
<p>
|
|
304
|
308
|
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 haul 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.
|
|
305
|
309
|
</p>
|
|
306
|
310
|
</div>
|
|
307
|
|
-<div id="outline-container-org24036e7" class="outline-4">
|
|
308
|
|
-<h4 id="org24036e7">Beaglebone Black</h4>
|
|
309
|
|
-<div class="outline-text-4" id="text-org24036e7">
|
|
|
311
|
+<div id="outline-container-org19a77dc" class="outline-4">
|
|
|
312
|
+<h4 id="org19a77dc">Beaglebone Black</h4>
|
|
|
313
|
+<div class="outline-text-4" id="text-org19a77dc">
|
|
310
|
314
|
<div class="org-src-container">
|
|
311
|
315
|
|
|
312
|
316
|
<pre class="src src-bash">sudo apt-get install xz-utils wget
|
|
|
@@ -319,14 +323,18 @@ unxz mesh-router-beaglebone-black.img.xz
|
|
319
|
323
|
sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=mesh-router-beaglebone-black.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
|
|
320
|
324
|
</pre>
|
|
321
|
325
|
</div>
|
|
|
326
|
+
|
|
|
327
|
+<p>
|
|
|
328
|
+If you have a few Beaglebone Blacks to use as routers then repeat the <i>dd</i> command to create however many microSD cards you need.
|
|
|
329
|
+</p>
|
|
322
|
330
|
</div>
|
|
323
|
331
|
</div>
|
|
324
|
332
|
</div>
|
|
325
|
333
|
</div>
|
|
326
|
334
|
|
|
327
|
|
-<div id="outline-container-orgae92e8f" class="outline-2">
|
|
328
|
|
-<h2 id="orgae92e8f">To build the disk image yourself</h2>
|
|
329
|
|
-<div class="outline-text-2" id="text-orgae92e8f">
|
|
|
335
|
+<div id="outline-container-org6aac01f" class="outline-2">
|
|
|
336
|
+<h2 id="org6aac01f">To build the disk image yourself</h2>
|
|
|
337
|
+<div class="outline-text-2" id="text-org6aac01f">
|
|
330
|
338
|
<p>
|
|
331
|
339
|
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.
|
|
332
|
340
|
</p>
|
|
|
@@ -421,9 +429,9 @@ The resulting image can be copied to a microSD card, inserted into a Beaglebone
|
|
421
|
429
|
</div>
|
|
422
|
430
|
</div>
|
|
423
|
431
|
|
|
424
|
|
-<div id="outline-container-orge48cc64" class="outline-2">
|
|
425
|
|
-<h2 id="orge48cc64">How to use it</h2>
|
|
426
|
|
-<div class="outline-text-2" id="text-orge48cc64">
|
|
|
432
|
+<div id="outline-container-org151877c" class="outline-2">
|
|
|
433
|
+<h2 id="org151877c">How to use it</h2>
|
|
|
434
|
+<div class="outline-text-2" id="text-org151877c">
|
|
427
|
435
|
<p>
|
|
428
|
436
|
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.
|
|
429
|
437
|
</p>
|
Bob Mottram
il y a 8 ans