Explorar el Código

Advice on connecting the mesh to the internet

Bob Mottram hace 7 años
padre
commit
f47d107f98
Se han modificado 2 ficheros con 72 adiciones y 56 borrados
  1. 4
    0
      doc/EN/mesh.org
  2. 68
    56
      website/EN/mesh.html

+ 4
- 0
doc/EN/mesh.org Ver fichero

@@ -228,6 +228,10 @@ Select the wifi icon on the desktop and enter the password '/freedombone/'. The
228 228
 #+END_CENTER
229 229
 
230 230
 When you are finished close the window and then select the /Network Restart/ desktop icon, which will restart the B.A.T.M.A.N. network. You can also use the restart icon if you are within range of the mesh network but the /Chat/ and /Other Users/ icons do not automatically appear after a few minutes.
231
+** Connecting to the internet
232
+If you need to be able to access the internet from the mesh then connect one of the peers to an internet router using an ethernet cable, then reboot it. Other peers in the mesh, including any attached mobile devices, will then be able to access the internet using the ethernet attached peer as a gateway. [[https://en.wikipedia.org/wiki/Freifunk][Freifunk]] works in a similar way.
233
+
234
+After connecting one peer to the internet you may need to reboot other peers in order to update their network configurations.
231 235
 ** Mobile devices (phones, etc)
232 236
 To allow mobile devices to connect to the mesh you will need a second wifi adapter connected to your laptop/netbook/SBC. Plug in a second wifi adapter then reboot the system. The second adaptor will then create a wifi hotspot which mobile devices can connect to. The hotspot name also contains its local IP address (eg. "/mesh-192.168.1.83/").
233 237
 

+ 68
- 56
website/EN/mesh.html Ver fichero

@@ -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
-<!-- 2017-10-05 Thu 13:04 -->
6
+<!-- 2017-10-05 Thu 13:13 -->
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>&lrm;</title>
@@ -274,13 +274,13 @@ for the JavaScript code in this tag.
274 274
 </colgroup>
275 275
 <tbody>
276 276
 <tr>
277
-<td class="org-left"><a href="#org31db069">What the system can do</a></td>
277
+<td class="org-left"><a href="#orge7e03ce">What the system can do</a></td>
278 278
 <td class="org-left">-</td>
279
-<td class="org-left"><a href="#org591eab6">Disk Images</a></td>
279
+<td class="org-left"><a href="#orgc3dbd7e">Disk Images</a></td>
280 280
 <td class="org-left">-</td>
281
-<td class="org-left"><a href="#orgfd2a746">Building Disk Images</a></td>
281
+<td class="org-left"><a href="#orgf01fd55">Building Disk Images</a></td>
282 282
 <td class="org-left">-</td>
283
-<td class="org-left"><a href="#orgf02b56e">How to use it</a></td>
283
+<td class="org-left"><a href="#org1e57e4d">How to use it</a></td>
284 284
 </tr>
285 285
 </tbody>
286 286
 </table>
@@ -324,9 +324,9 @@ The Freedombone mesh roughly follows MondoNet's ten social specifications:
324 324
 <li><b>Evolvable</b>: The network should be built with future development in mind. The platform should be flexible enough to support technologies, protocols and modes of usage that have not yet been developed.</li>
325 325
 </ul>
326 326
 
327
-<div id="outline-container-org31db069" class="outline-2">
328
-<h2 id="org31db069">What the system can do</h2>
329
-<div class="outline-text-2" id="text-org31db069">
327
+<div id="outline-container-orge7e03ce" class="outline-2">
328
+<h2 id="orge7e03ce">What the system can do</h2>
329
+<div class="outline-text-2" id="text-orge7e03ce">
330 330
 <ul class="org-ul">
331 331
 <li>Discovery of other users on the network</li>
332 332
 <li>Text based chat, one-to-one and in groups</li>
@@ -350,13 +350,13 @@ This system should be quite scalable. Both qTox and IPFS are based upon distribu
350 350
 </div>
351 351
 </div>
352 352
 
353
-<div id="outline-container-org591eab6" class="outline-2">
354
-<h2 id="org591eab6">Disk Images</h2>
355
-<div class="outline-text-2" id="text-org591eab6">
353
+<div id="outline-container-orgc3dbd7e" class="outline-2">
354
+<h2 id="orgc3dbd7e">Disk Images</h2>
355
+<div class="outline-text-2" id="text-orgc3dbd7e">
356 356
 </div>
357
-<div id="outline-container-orgffdec7f" class="outline-3">
358
-<h3 id="orgffdec7f">Writing many images quickly</h3>
359
-<div class="outline-text-3" id="text-orgffdec7f">
357
+<div id="outline-container-org48cf6b4" class="outline-3">
358
+<h3 id="org48cf6b4">Writing many images quickly</h3>
359
+<div class="outline-text-3" id="text-org48cf6b4">
360 360
 <p>
361 361
 There may be situations where you need to write the same disk image to multiple drives at the same time in order to maximize rate of deployment. In the instructions given below the <b>dd</b> command is used for writing to the target drive, but to write to multiple drives you can use a tool such as <a href="https://wiki.gnome.org/Apps/MultiWriter">GNOME MultiWriter</a>.
362 362
 </p>
@@ -384,9 +384,9 @@ The MultiWriter tool is also available within mesh client images, so that you ca
384 384
 </p>
385 385
 </div>
386 386
 </div>
387
-<div id="outline-container-org4e60223" class="outline-3">
388
-<h3 id="org4e60223">Client images</h3>
389
-<div class="outline-text-3" id="text-org4e60223">
387
+<div id="outline-container-orga4d8a06" class="outline-3">
388
+<h3 id="orga4d8a06">Client images</h3>
389
+<div class="outline-text-3" id="text-orga4d8a06">
390 390
 <div class="org-center">
391 391
 
392 392
 <div class="figure">
@@ -435,16 +435,16 @@ sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-n
435 435
 </div>
436 436
 </div>
437 437
 
438
-<div id="outline-container-org619ed5c" class="outline-3">
439
-<h3 id="org619ed5c">Router images</h3>
440
-<div class="outline-text-3" id="text-org619ed5c">
438
+<div id="outline-container-org990631a" class="outline-3">
439
+<h3 id="org990631a">Router images</h3>
440
+<div class="outline-text-3" id="text-org990631a">
441 441
 <p>
442 442
 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 and to enable peers to find each other via running bootstrap nodes for Tox and IPFS. 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.
443 443
 </p>
444 444
 </div>
445
-<div id="outline-container-orga6faa1b" class="outline-4">
446
-<h4 id="orga6faa1b">Beaglebone Black</h4>
447
-<div class="outline-text-4" id="text-orga6faa1b">
445
+<div id="outline-container-orgf4481d1" class="outline-4">
446
+<h4 id="orgf4481d1">Beaglebone Black</h4>
447
+<div class="outline-text-4" id="text-orgf4481d1">
448 448
 <div class="org-center">
449 449
 
450 450
 <div class="figure">
@@ -481,9 +481,9 @@ There is still a software freedom issue with the Beaglebone Black, but it doesn'
481 481
 </div>
482 482
 </div>
483 483
 
484
-<div id="outline-container-orgfd2a746" class="outline-2">
485
-<h2 id="orgfd2a746">Building Disk Images</h2>
486
-<div class="outline-text-2" id="text-orgfd2a746">
484
+<div id="outline-container-orgf01fd55" class="outline-2">
485
+<h2 id="orgf01fd55">Building Disk Images</h2>
486
+<div class="outline-text-2" id="text-orgf01fd55">
487 487
 <p>
488 488
 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.
489 489
 </p>
@@ -571,9 +571,9 @@ The resulting image can be copied to a microSD card, inserted into a Beaglebone
571 571
 </div>
572 572
 </div>
573 573
 
574
-<div id="outline-container-org70ededa" class="outline-2">
575
-<h2 id="org70ededa">Customisation</h2>
576
-<div class="outline-text-2" id="text-org70ededa">
574
+<div id="outline-container-org410f58b" class="outline-2">
575
+<h2 id="org410f58b">Customisation</h2>
576
+<div class="outline-text-2" id="text-org410f58b">
577 577
 <p>
578 578
 If you want to make your own specially branded version, such as for a particular event, then to change the default desktop backgrounds edit the images within <b>img/backgrounds</b> and to change the available avatars and desktop icons edit the images within <b>img/avatars</b>. Re-create disk images using the instructions shown previously.
579 579
 </p>
@@ -583,9 +583,9 @@ If you need particular <i>dconf</i> commands to alter desktop appearance or beha
583 583
 </p>
584 584
 </div>
585 585
 </div>
586
-<div id="outline-container-orgf02b56e" class="outline-2">
587
-<h2 id="orgf02b56e">How to use it</h2>
588
-<div class="outline-text-2" id="text-orgf02b56e">
586
+<div id="outline-container-org1e57e4d" class="outline-2">
587
+<h2 id="org1e57e4d">How to use it</h2>
588
+<div class="outline-text-2" id="text-org1e57e4d">
589 589
 <p>
590 590
 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.
591 591
 </p>
@@ -595,9 +595,9 @@ After a minute or two if you are within wifi range and there is at least one oth
595 595
 </p>
596 596
 </div>
597 597
 
598
-<div id="outline-container-org6725f18" class="outline-3">
599
-<h3 id="org6725f18">Boot trouble</h3>
600
-<div class="outline-text-3" id="text-org6725f18">
598
+<div id="outline-container-org11d6908" class="outline-3">
599
+<h3 id="org11d6908">Boot trouble</h3>
600
+<div class="outline-text-3" id="text-org11d6908">
601 601
 <p>
602 602
 If the system doesn't boot and reports an error which includes <b>/dev/mapper/loop0p1</b> then reboot with <b>Ctrl-Alt-Del</b> and when you see the grub menu press <b>e</b> and manually change <b>/dev/mapper/loop0p1</b> to <b>/dev/sdb1</b>, then press <b>Ctrl-x</b>. If that doesn't work then reboot and try <b>/dev/sdc1</b> instead.
603 603
 </p>
@@ -607,9 +607,9 @@ After the system has booted successfully the problem should resolve itself on su
607 607
 </p>
608 608
 </div>
609 609
 </div>
610
-<div id="outline-container-org3e04c3e" class="outline-3">
611
-<h3 id="org3e04c3e">Set the Date</h3>
612
-<div class="outline-text-3" id="text-org3e04c3e">
610
+<div id="outline-container-org17e82b1" class="outline-3">
611
+<h3 id="org17e82b1">Set the Date</h3>
612
+<div class="outline-text-3" id="text-org17e82b1">
613 613
 <p>
614 614
 On the ordinary internet the date and time of your system would be set automatically via NTP. But this is not the internet and so you will need to manually ensure that your date and time settings are correct. You might need to periodically do this if your clock drifts. It's not essential that the time on your system be highly accurate, but if it drifts too far or goes back to epoch then things could become a little confusing in regard to the order of blog posts.
615 615
 </p>
@@ -619,9 +619,9 @@ On the ordinary internet the date and time of your system would be set automatic
619 619
 </p>
620 620
 </div>
621 621
 </div>
622
-<div id="outline-container-org0643cbc" class="outline-3">
623
-<h3 id="org0643cbc">Check network status</h3>
624
-<div class="outline-text-3" id="text-org0643cbc">
622
+<div id="outline-container-org55b78da" class="outline-3">
623
+<h3 id="org55b78da">Check network status</h3>
624
+<div class="outline-text-3" id="text-org55b78da">
625 625
 <p>
626 626
 Unlike with ordinary wifi, on the mesh you don't get a signal strength icon and so it's not simple to see if you have a good connection.
627 627
 </p>
@@ -644,9 +644,21 @@ When you are finished close the window and then select the <i>Network Restart</i
644 644
 </p>
645 645
 </div>
646 646
 </div>
647
-<div id="outline-container-org4218a50" class="outline-3">
648
-<h3 id="org4218a50">Mobile devices (phones, etc)</h3>
649
-<div class="outline-text-3" id="text-org4218a50">
647
+<div id="outline-container-orgc3d9324" class="outline-3">
648
+<h3 id="orgc3d9324">Connecting to the internet</h3>
649
+<div class="outline-text-3" id="text-orgc3d9324">
650
+<p>
651
+If you need to be able to access the internet from the mesh then connect one of the peers to an internet router using an ethernet cable, then reboot it. Other peers in the mesh, including any attached mobile devices, will then be able to access the internet using the ethernet attached peer as a gateway. <a href="https://en.wikipedia.org/wiki/Freifunk">Freifunk</a> works in a similar way.
652
+</p>
653
+
654
+<p>
655
+After connecting one peer to the internet you may need to reboot other peers in order to update their network configurations.
656
+</p>
657
+</div>
658
+</div>
659
+<div id="outline-container-orgdceba0f" class="outline-3">
660
+<h3 id="orgdceba0f">Mobile devices (phones, etc)</h3>
661
+<div class="outline-text-3" id="text-orgdceba0f">
650 662
 <p>
651 663
 To allow mobile devices to connect to the mesh you will need a second wifi adapter connected to your laptop/netbook/SBC. Plug in a second wifi adapter then reboot the system. The second adaptor will then create a wifi hotspot which mobile devices can connect to. The hotspot name also contains its local IP address (eg. "<i>mesh-192.168.1.83</i>").
652 664
 </p>
@@ -668,9 +680,9 @@ On some android devices you may need to move the downloaded APK file from the <b
668 680
 </p>
669 681
 </div>
670 682
 </div>
671
-<div id="outline-container-org83ac204" class="outline-3">
672
-<h3 id="org83ac204">Chat System</h3>
673
-<div class="outline-text-3" id="text-org83ac204">
683
+<div id="outline-container-org6f1f090" class="outline-3">
684
+<h3 id="org6f1f090">Chat System</h3>
685
+<div class="outline-text-3" id="text-org6f1f090">
674 686
 <p>
675 687
 Ensure that you're within wifi range of at least one other mesh peer (could be a router or client) and then you should see that the <i>Chat</i> and <i>Other Users</i> icons appear. Select the users icon and you should see a list of users on the mesh. Select the <i>Chat</i> icon and once you are connected you should see the status light turn green. If after a few minutes you don't get the green status light then try closing and re-opening the Tox chat application. Select the plus button to add a friend and then copy and paste in a Tox ID from the users list.
676 688
 </p>
@@ -729,9 +741,9 @@ At present video doesn't work reliably, but text and voice chat do work well.
729 741
 </div>
730 742
 </div>
731 743
 
732
-<div id="outline-container-org7cefd77" class="outline-3">
733
-<h3 id="org7cefd77">Social Network</h3>
734
-<div class="outline-text-3" id="text-org7cefd77">
744
+<div id="outline-container-org8ac8f7d" class="outline-3">
745
+<h3 id="org8ac8f7d">Social Network</h3>
746
+<div class="outline-text-3" id="text-org8ac8f7d">
735 747
 <p>
736 748
 Patchwork is available as a social networking system for the mesh. Like all social network systems it has a stream of posts and you can follow or unfollow other users. You can also send private messages to other users with end-to-end encryption.
737 749
 </p>
@@ -766,9 +778,9 @@ The Secure Scuttlebutt protocol which Patchwork is based upon is intended to be
766 778
 </div>
767 779
 </div>
768 780
 
769
-<div id="outline-container-org1d48b53" class="outline-3">
770
-<h3 id="org1d48b53">Sharing Files</h3>
771
-<div class="outline-text-3" id="text-org1d48b53">
781
+<div id="outline-container-org25fbdb4" class="outline-3">
782
+<h3 id="org25fbdb4">Sharing Files</h3>
783
+<div class="outline-text-3" id="text-org25fbdb4">
772 784
 <p>
773 785
 You can make files publicly available on the network simply by dragging and dropping them into the <i>Public</i> folder on the desktop. To view the files belonging to another user select the desktop icon called <i>Visit a site</i> and enter the username or Tox ID of the other user.
774 786
 </p>
@@ -783,9 +795,9 @@ You can make files publicly available on the network simply by dragging and drop
783 795
 </div>
784 796
 </div>
785 797
 
786
-<div id="outline-container-org152b28b" class="outline-3">
787
-<h3 id="org152b28b">Blogging</h3>
788
-<div class="outline-text-3" id="text-org152b28b">
798
+<div id="outline-container-org00ad2c3" class="outline-3">
799
+<h3 id="org00ad2c3">Blogging</h3>
800
+<div class="outline-text-3" id="text-org00ad2c3">
789 801
 <p>
790 802
 To create a blog post select the <i>Blog</i> icon on the desktop and then use the up and down cursor keys, space bar and enter key to add a new entry. Edit the title of the entry and add your text. You can also include photos if you wish - just copy them to the <b>CreateBlog/content/images</b> directory and then link to them as shown.
791 803
 </p>