Skip to content
Snippets Groups Projects
Commit 89ed692b authored by Bob Mottram's avatar Bob Mottram
Browse files

mesh documentation

parent e0d61a09
No related branches found
No related tags found
No related merge requests found
......@@ -35,6 +35,8 @@ unxz mesh-client-i386.img.xz
sudo dd bs=1M if=mesh-client-i386.img of=/dev/sdX conv=fdatasync
#+end_src
To get a number of systems onto the mesh repeat the /dd/ command to create however many bootable USB drives you need.
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 *are not recommended* 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.
#+begin_src bash
......@@ -62,6 +64,8 @@ unxz mesh-router-beaglebone-black.img.xz
sudo dd bs=1M if=mesh-router-beaglebone-black.img of=/dev/sdX conv=fdatasync
#+end_src
If you have a few Beaglebone Blacks to use as routers then repeat the /dd/ command to create however many microSD cards you need.
* To build the disk image yourself
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.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment