瀏覽代碼

Update documentation

Bob Mottram 9 年之前
父節點
當前提交
e14c72b32a
沒有帳戶連結到提交者的電子郵件
共有 2 個文件被更改,包括 105 次插入27 次删除
  1. 24
    5
      doc/EN/mesh.org
  2. 81
    22
      website/EN/mesh.html

+ 24
- 5
doc/EN/mesh.org 查看文件

@@ -18,13 +18,32 @@
18 18
 [[file:images/mesh_screenshot.jpg]]
19 19
 #+END_CENTER
20 20
 
21
+|------------------------+---+-------------+---+----------------------+---+---------------|
22
+| [[What the system can do]] | - | [[Disk Images]] | - | [[Building Disk Images]] | - | [[How to use it]] |
23
+|------------------------+---+-------------+---+----------------------+---+---------------|
24
+
21 25
 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, temporary "digital blackouts", scientific expeditions and off-world space colonies. 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.
22 26
 
23
- * [[Ready made images]]
24
- * [[To build the disk image yourself]]
25
- * [[How to use it]]
27
+* What the system can do
28
+
29
+ - Discovery of other users on the network
30
+ - Text based chat, one-to-one and in groups
31
+ - Voice chat (VoIP)
32
+ - Private and public sharing of files
33
+ - Blogging
34
+ - No network administration required
35
+
36
+Communication is local between systems within wifi range of each other. If systems are out of wifi range the data is mesh routed through intermediate peers.
37
+
38
+No servers, internet connection or cabling is needed.
39
+
40
+Works from bootable USB drives or microSD drives.
41
+
42
+Private communications is end-to-end secured with elliptic curve encryption and is forward secret. Not easy to censor or passively monitor.
43
+
44
+Publicly shared data is /content addressable/ and therefore scalable to many peers.
26 45
 
27
-* Ready made images
46
+* Disk Images
28 47
 ** Client images
29 48
 
30 49
 #+BEGIN_CENTER
@@ -81,7 +100,7 @@ sudo dd bs=1M if=mesh-router-beaglebone-black.img of=/dev/sdX conv=fdatasync
81 100
 
82 101
 If you have a few Beaglebone Blacks to use as routers then repeat the /dd/ command to create however many microSD cards you need.
83 102
 
84
-* To build the disk image yourself
103
+* Building Disk Images
85 104
 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.
86 105
 
87 106
 First you will need to create an image. On a Debian based system (tested on Debian Jessie and Trisquel 7):

+ 81
- 22
website/EN/mesh.html 查看文件

@@ -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-09-01 Thu 13:02 -->
6
+<!-- 2016-09-09 Fri 20:10 -->
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>
@@ -252,22 +252,81 @@ for the JavaScript code in this tag.
252 252
 </div>
253 253
 </div>
254 254
 
255
+<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
256
+
257
+
258
+<colgroup>
259
+<col  class="org-left" />
260
+
261
+<col  class="org-left" />
262
+
263
+<col  class="org-left" />
264
+
265
+<col  class="org-left" />
266
+
267
+<col  class="org-left" />
268
+
269
+<col  class="org-left" />
270
+
271
+<col  class="org-left" />
272
+</colgroup>
273
+<tbody>
274
+<tr>
275
+<td class="org-left"><a href="#org707c257">What the system can do</a></td>
276
+<td class="org-left">-</td>
277
+<td class="org-left"><a href="#orgd00db33">Disk Images</a></td>
278
+<td class="org-left">-</td>
279
+<td class="org-left"><a href="#org0840eb8">Building Disk Images</a></td>
280
+<td class="org-left">-</td>
281
+<td class="org-left"><a href="#orga6e8ab2">How to use it</a></td>
282
+</tr>
283
+</tbody>
284
+</table>
285
+
255 286
 <p>
256 287
 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, temporary "digital blackouts", scientific expeditions and off-world space colonies. 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.
257 288
 </p>
258 289
 
290
+<div id="outline-container-org707c257" class="outline-2">
291
+<h2 id="org707c257">What the system can do</h2>
292
+<div class="outline-text-2" id="text-org707c257">
259 293
 <ul class="org-ul">
260
-<li><a href="#org293e8ad">Ready made images</a></li>
261
-<li><a href="#org139ec0d">To build the disk image yourself</a></li>
262
-<li><a href="#org1a4a0ff">How to use it</a></li>
294
+<li>Discovery of other users on the network</li>
295
+<li>Text based chat, one-to-one and in groups</li>
296
+<li>Voice chat (VoIP)</li>
297
+<li>Private and public sharing of files</li>
298
+<li>Blogging</li>
299
+<li>No network administration required</li>
263 300
 </ul>
264 301
 
265
-<div id="outline-container-org293e8ad" class="outline-2">
266
-<h2 id="org293e8ad">Ready made images</h2>
267
-<div class="outline-text-2" id="text-org293e8ad">
268
-</div><div id="outline-container-org97a6f70" class="outline-3">
269
-<h3 id="org97a6f70">Client images</h3>
270
-<div class="outline-text-3" id="text-org97a6f70">
302
+<p>
303
+Communication is local between systems within wifi range of each other. If systems are out of wifi range the data is mesh routed through intermediate peers.
304
+</p>
305
+
306
+<p>
307
+No servers, internet connection or cabling is needed.
308
+</p>
309
+
310
+<p>
311
+Works from bootable USB drives or microSD drives.
312
+</p>
313
+
314
+<p>
315
+Private communications is end-to-end secured with elliptic curve encryption and is forward secret. Not easy to censor or passively monitor.
316
+</p>
317
+
318
+<p>
319
+Publicly shared data is <i>content addressable</i> and therefore scalable to many peers.
320
+</p>
321
+</div>
322
+</div>
323
+
324
+<div id="outline-container-orgd00db33" class="outline-2">
325
+<h2 id="orgd00db33">Disk Images</h2>
326
+<div class="outline-text-2" id="text-orgd00db33">
327
+</div><div id="outline-container-orgb5d2863" class="outline-3">
328
+<h3 id="orgb5d2863">Client images</h3>
329
+<div class="outline-text-3" id="text-orgb5d2863">
271 330
 <div class="org-center">
272 331
 
273 332
 <div class="figure">
@@ -316,16 +375,16 @@ sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-n
316 375
 </div>
317 376
 </div>
318 377
 
319
-<div id="outline-container-org29332d7" class="outline-3">
320
-<h3 id="org29332d7">Router images</h3>
321
-<div class="outline-text-3" id="text-org29332d7">
378
+<div id="outline-container-orgd6a576d" class="outline-3">
379
+<h3 id="orgd6a576d">Router images</h3>
380
+<div class="outline-text-3" id="text-orgd6a576d">
322 381
 <p>
323 382
 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.
324 383
 </p>
325 384
 </div>
326
-<div id="outline-container-org696f207" class="outline-4">
327
-<h4 id="org696f207">Beaglebone Black</h4>
328
-<div class="outline-text-4" id="text-org696f207">
385
+<div id="outline-container-org2908ddf" class="outline-4">
386
+<h4 id="org2908ddf">Beaglebone Black</h4>
387
+<div class="outline-text-4" id="text-org2908ddf">
329 388
 <div class="org-center">
330 389
 
331 390
 <div class="figure">
@@ -359,9 +418,9 @@ If you have a few Beaglebone Blacks to use as routers then repeat the <i>dd</i>
359 418
 </div>
360 419
 </div>
361 420
 
362
-<div id="outline-container-org139ec0d" class="outline-2">
363
-<h2 id="org139ec0d">To build the disk image yourself</h2>
364
-<div class="outline-text-2" id="text-org139ec0d">
421
+<div id="outline-container-org0840eb8" class="outline-2">
422
+<h2 id="org0840eb8">Building Disk Images</h2>
423
+<div class="outline-text-2" id="text-org0840eb8">
365 424
 <p>
366 425
 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.
367 426
 </p>
@@ -456,9 +515,9 @@ The resulting image can be copied to a microSD card, inserted into a Beaglebone
456 515
 </div>
457 516
 </div>
458 517
 
459
-<div id="outline-container-org1a4a0ff" class="outline-2">
460
-<h2 id="org1a4a0ff">How to use it</h2>
461
-<div class="outline-text-2" id="text-org1a4a0ff">
518
+<div id="outline-container-orga6e8ab2" class="outline-2">
519
+<h2 id="orga6e8ab2">How to use it</h2>
520
+<div class="outline-text-2" id="text-orga6e8ab2">
462 521
 <p>
463 522
 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.
464 523
 </p>