Differences

This shows you the differences between two versions of the page.

--- mesh [2025/11/29 05:41] – n6cta
+++ mesh [2026/01/02 17:43] (current) – kc2ihx
@@ Line 1: / Line 1: @@
+====== FARPN Mesh =====
+We currently have two mesh projects. The first mesh is Yggdrasil which is an E2EE IPv6 overlay mesh which is Layer 3. Reticulum is the other mesh technology we are playing with. Reticulum doesn't fit neatly into the OSI model; we run it both as a Layer 3 mesh via Yggdrasil and as a Layer 2 mesh via LoRA.
 ===== Yggdrasil =====
@@ Line 5: / Line 8: @@
 Generate [[https://yggdrasil-network.github.io/configuration.html|a configuration file]] for your system and restart the `yggdrasil` service. Don't just create the file, generate it the right way.
-One Debian systems that'll look like this:
+One Debian systems that'll look like this -- create the file first in a directory where you have write permissions:
-  sudo yggdrasil -genconf -json > /etc/yggdrasil/yggdrasil.conf
+  sudo yggdrasil -genconf -json > yggdrasil.conf
+Note that you can't create this file directly in the ''/etc/yggdrasil/'' directory where the service looks for it.
 In the `yggdrasil.conf` file, edit your peers to add:
@@ Line 23: / Line 28: @@
   "Peer Type": "Bootstrap Gateway"
   }
+Then copy the resulting file to ''/etc/yggdrasil/yggdrasil.conf'' and start the yggdrasil service:
+   sudo cp yggdrasil.conf /etc/yggdrasil/yggdrasil.conf
+   sudo systemctl enable yggdrasil
+   sudo systemctl start yggdrasil
+Check the status with:
+   sudo systemctl status yggdrasil
+If the service failed, check the ''yggdrasil.conf'' file for syntax issues, and check the permissions on the file.  It should be owned by ''root'' and the ''yggdrasil'' group.
 ===== Reticulum =====
@@ Line 44: / Line 61: @@
     configured_bitrate = None
+===== Yggdrasil Public Keys =====
+^ Name     ^ Callsign   ^ Public Key                                                              ^
-^ Name      ^ Callsign       ^ Public Key          ^
 | Scott    | VE3QBZ     | 0000000e83773b7a3931dd2d0847df6b18d4f005e391bd985601863985db3ff0        |
 | Chris    | N6CTA      | 6225163ce09e8ab44732f093602905daf8f66621908c90b154340ce43c09f22f        |
 | Emily    | W1EML      | 2bcb980826952676c61cd3b22b5656958e7cdd509d9ada8fb38fd01a841578ef        |
 | Evan     | KC2IHX     | 413024abc35ae3e8fe1152a935a84f9406f8aa00bf54dbc21f4837671f7fb23b	  |
-| Matt     | W1CDN      | 736a4da2aeb0489f456eb1fbd1398614245b6dc7fa910be49e1b1531d1f69ee4        |
+| Matt     | W1CDN      | aa6b519c2ba5b9f53f434c32d54b91ce57517bd21d8390725fad504ca4c4f8aa        |
 | Tony     | VK3JED     | 6f11bb6b75b617ed7e5a96cc0cdfc31236916d09906a8ed52bfae9c72c332492        |
-Boilerplate whitelist for /etc/yggdrasil/yggdrasil.conf
-(WIP, do not use yet)
-<code>
-# List of peer public keys to allow incoming peering connections
-# from. If left empty/undefined then all connections will be allowed
-# by default. This does not affect outgoing peerings, nor does it
-# affect link-local peers discovered via multicast.
-# WARNING: THIS IS NOT A FIREWALL and DOES NOT limit who can reach
-# open ports or services running on your machine!
-  AllowedPublicKeys: []
-</code>