|
|
|
|
|
|
3
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
3
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
4
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
4
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
|
5
|
<head>
|
5
|
<head>
|
|
6
|
-<!-- 2016-09-01 Thu 10:55 -->
|
|
|
|
|
|
6
|
+<!-- 2016-09-01 Thu 11:31 -->
|
|
7
|
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
7
|
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
|
8
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
8
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
9
|
<title></title>
|
9
|
<title></title>
|
|
|
|
|
|
|
257
|
</p>
|
257
|
</p>
|
|
258
|
|
258
|
|
|
259
|
<ul class="org-ul">
|
259
|
<ul class="org-ul">
|
|
260
|
-<li><a href="#org760a031">Ready made images</a></li>
|
|
|
|
261
|
-<li><a href="#org800eb33">To build the disk image yourself</a></li>
|
|
|
|
262
|
-<li><a href="#org2f93077">How to use it</a></li>
|
|
|
|
|
|
260
|
+<li><a href="#org58fc760">Ready made images</a></li>
|
|
|
|
261
|
+<li><a href="#orgd79f2a2">To build the disk image yourself</a></li>
|
|
|
|
262
|
+<li><a href="#org1a1359a">How to use it</a></li>
|
|
263
|
</ul>
|
263
|
</ul>
|
|
264
|
|
264
|
|
|
265
|
-<div id="outline-container-org760a031" class="outline-2">
|
|
|
|
266
|
-<h2 id="org760a031">Ready made images</h2>
|
|
|
|
267
|
-<div class="outline-text-2" id="text-org760a031">
|
|
|
|
268
|
-</div><div id="outline-container-org66c2a01" class="outline-3">
|
|
|
|
269
|
-<h3 id="org66c2a01">Client images</h3>
|
|
|
|
270
|
-<div class="outline-text-3" id="text-org66c2a01">
|
|
|
|
|
|
265
|
+<div id="outline-container-org58fc760" class="outline-2">
|
|
|
|
266
|
+<h2 id="org58fc760">Ready made images</h2>
|
|
|
|
267
|
+<div class="outline-text-2" id="text-org58fc760">
|
|
|
|
268
|
+</div><div id="outline-container-org8b67c9e" class="outline-3">
|
|
|
|
269
|
+<h3 id="org8b67c9e">Client images</h3>
|
|
|
|
270
|
+<div class="outline-text-3" id="text-org8b67c9e">
|
|
271
|
<p>
|
271
|
<p>
|
|
272
|
"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).
|
272
|
"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).
|
|
273
|
</p>
|
273
|
</p>
|
|
|
|
|
|
|
308
|
</div>
|
308
|
</div>
|
|
309
|
</div>
|
309
|
</div>
|
|
310
|
|
310
|
|
|
311
|
-<div id="outline-container-org67334a7" class="outline-3">
|
|
|
|
312
|
-<h3 id="org67334a7">Router images</h3>
|
|
|
|
313
|
-<div class="outline-text-3" id="text-org67334a7">
|
|
|
|
|
|
311
|
+<div id="outline-container-orgcde0031" class="outline-3">
|
|
|
|
312
|
+<h3 id="orgcde0031">Router images</h3>
|
|
|
|
313
|
+<div class="outline-text-3" id="text-orgcde0031">
|
|
314
|
<p>
|
314
|
<p>
|
|
315
|
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.
|
315
|
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.
|
|
316
|
</p>
|
316
|
</p>
|
|
317
|
</div>
|
317
|
</div>
|
|
318
|
-<div id="outline-container-org6711b0a" class="outline-4">
|
|
|
|
319
|
-<h4 id="org6711b0a">Beaglebone Black</h4>
|
|
|
|
320
|
-<div class="outline-text-4" id="text-org6711b0a">
|
|
|
|
|
|
318
|
+<div id="outline-container-org7419bac" class="outline-4">
|
|
|
|
319
|
+<h4 id="org7419bac">Beaglebone Black</h4>
|
|
|
|
320
|
+<div class="outline-text-4" id="text-org7419bac">
|
|
321
|
<div class="org-src-container">
|
321
|
<div class="org-src-container">
|
|
322
|
|
322
|
|
|
323
|
<pre class="src src-bash">sudo apt-get install xz-utils wget
|
323
|
<pre class="src src-bash">sudo apt-get install xz-utils wget
|
|
|
|
|
|
|
339
|
</div>
|
339
|
</div>
|
|
340
|
</div>
|
340
|
</div>
|
|
341
|
|
341
|
|
|
342
|
-<div id="outline-container-org800eb33" class="outline-2">
|
|
|
|
343
|
-<h2 id="org800eb33">To build the disk image yourself</h2>
|
|
|
|
344
|
-<div class="outline-text-2" id="text-org800eb33">
|
|
|
|
|
|
342
|
+<div id="outline-container-orgd79f2a2" class="outline-2">
|
|
|
|
343
|
+<h2 id="orgd79f2a2">To build the disk image yourself</h2>
|
|
|
|
344
|
+<div class="outline-text-2" id="text-orgd79f2a2">
|
|
345
|
<p>
|
345
|
<p>
|
|
346
|
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.
|
346
|
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.
|
|
347
|
</p>
|
347
|
</p>
|
|
348
|
|
348
|
|
|
349
|
<p>
|
349
|
<p>
|
|
350
|
-First you will need to create an image. On a Debian based system:
|
|
|
|
|
|
350
|
+First you will need to create an image. On a Debian based system (tested on Debian Jessie and Trisquel 7):
|
|
351
|
</p>
|
351
|
</p>
|
|
352
|
|
352
|
|
|
353
|
<div class="org-src-container">
|
353
|
<div class="org-src-container">
|
|
354
|
|
354
|
|
|
355
|
-<pre class="src src-bash">sudo su
|
|
|
|
356
|
-apt-get -y install build-essential libc6-dev-i386 <span class="org-sh-escaped-newline">\</span>
|
|
|
|
|
|
355
|
+<pre class="src src-bash">sudo apt-get -y install build-essential libc6-dev-i386 wget <span class="org-sh-escaped-newline">\</span>
|
|
357
|
gcc-multilib g++-multilib git python-docutils mktorrent <span class="org-sh-escaped-newline">\</span>
|
356
|
gcc-multilib g++-multilib git python-docutils mktorrent <span class="org-sh-escaped-newline">\</span>
|
|
358
|
vmdebootstrap xz-utils dosfstools btrfs-tools extlinux <span class="org-sh-escaped-newline">\</span>
|
357
|
vmdebootstrap xz-utils dosfstools btrfs-tools extlinux <span class="org-sh-escaped-newline">\</span>
|
|
359
|
python-distro-info mbr qemu-user-static binfmt-support <span class="org-sh-escaped-newline">\</span>
|
358
|
python-distro-info mbr qemu-user-static binfmt-support <span class="org-sh-escaped-newline">\</span>
|
|
360
|
u-boot-tools qemu
|
359
|
u-boot-tools qemu
|
|
361
|
-git clone https://github.com/bashrc/freedombone
|
|
|
|
|
|
360
|
+wget https://freedombone.net/downloads/freedombone-mesh-source.tar.gz
|
|
|
|
361
|
+wget https://freedombone.net/downloads/freedombone-mesh-source.tar.gz.sig
|
|
|
|
362
|
+gpg --verify freedombone-mesh-source.tar.gz.sig
|
|
|
|
363
|
+sha256sum freedombone-mesh-source.tar.gz
|
|
|
|
364
|
+912a881e32c2846337f19d60bc4685f745b252858b8bccb5d07d009e67c80c33
|
|
|
|
365
|
+tar -xzvf freedombone-mesh-source.tar.gz
|
|
362
|
<span class="org-builtin">cd</span> freedombone
|
366
|
<span class="org-builtin">cd</span> freedombone
|
|
363
|
git checkout stockholm
|
367
|
git checkout stockholm
|
|
364
|
-make install
|
|
|
|
|
|
368
|
+sudo make install
|
|
365
|
freedombone-image -t i386 -v meshclient
|
369
|
freedombone-image -t i386 -v meshclient
|
|
366
|
</pre>
|
370
|
</pre>
|
|
367
|
</div>
|
371
|
</div>
|
|
|
|
|
|
|
400
|
|
404
|
|
|
401
|
<div class="org-src-container">
|
405
|
<div class="org-src-container">
|
|
402
|
|
406
|
|
|
403
|
-<pre class="src src-bash">dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=myimagefile.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
|
|
|
|
|
|
407
|
+<pre class="src src-bash">sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=myimagefile.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
|
|
404
|
</pre>
|
408
|
</pre>
|
|
405
|
</div>
|
409
|
</div>
|
|
406
|
|
410
|
|
|
|
|
|
|
|
432
|
</div>
|
436
|
</div>
|
|
433
|
</div>
|
437
|
</div>
|
|
434
|
|
438
|
|
|
435
|
-<div id="outline-container-org2f93077" class="outline-2">
|
|
|
|
436
|
-<h2 id="org2f93077">How to use it</h2>
|
|
|
|
437
|
-<div class="outline-text-2" id="text-org2f93077">
|
|
|
|
|
|
439
|
+<div id="outline-container-org1a1359a" class="outline-2">
|
|
|
|
440
|
+<h2 id="org1a1359a">How to use it</h2>
|
|
|
|
441
|
+<div class="outline-text-2" id="text-org1a1359a">
|
|
438
|
<p>
|
442
|
<p>
|
|
439
|
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.
|
443
|
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.
|
|
440
|
</p>
|
444
|
</p>
|
Bob Mottram
8 年前