Skip to content
Go to file
Cannot retrieve contributors at this time
223 lines (156 sloc) 8.7 KB

Sudo Mesh Service Setup Guide

This guide is intended to help mesh node operators to:

  • decide what service might work well on a mesh network
  • implement their service
  • make their service accessible on the mesh (and the Internet?)
  • maintain their service
  • teach others to set up services

So you want to put a service on the mesh...

Maybe you just became a node on a mesh network, or maybe you'd like to learn more about how services work on a mesh. Whatever the case, you probably have a great idea for a service that could run on a distributed network. However, the first step is learn the concepts of meshing by building your own node.

build a mesh node

To host a service on a mesh, you must first be a node on said mesh. A mesh node can be almost any laptop, server, raspberry pi, or home router. To be part of a mesh, a device must be capable of three tasks:

  • running a mesh routing protocol (e.g. babel-d)
  • obtaining a mesh IP address (either statically from a server or via a distributed method, such mDNS)
  • digging a tunnel to the exit node (assuming that you'd like to connect to the world outside the mesh, or have only virtual connections to the mesh)

running babeld

babeld is how mesh nodes say hi, talk to one another, tell eachother about their neighbors. A great place to start learning about babel-d is our babeld-lab.

getting a mesh IP

Currently sudomesh uses a centralized database to manage IP address assignment, ensuring that there are no duplicate IPs handed out. This is a temporary solution until a distributed one is developed. Use makenode to get a sudomesh IP or figure out how to deploy your own meshnode database.

digging a tunnel

Even if you do not have a physical connection to the mesh, you can still be part of the mesh. By digging a tunnel through a VPN to the exit node, your mesh node can be connected to every other mesh node. It also functions as a way to connect to the broader internet. sudomesh uses the tunneldigger developed by wlanslovenija. Check out our tunneldigger-lab to get started.

Use Case - Raspberry Pi as wired mesh node via home node.


1 home node

1 raspberry pi running raspian with ssh enabled (see

1 computer connected to home node via ssid

1 human that is somewhat familiar with linux on commandline .

the use case assumed your computer is running ubuntu compatible flavor.


  1. figure out the home node ip by running ip route on the commandline. You should see something like :
$ ip route
default via 100.65.xx.xx dev wlp3s0  proto static  metric 600 

The first number 100.65.xx.xx is the ip address of your router on the mesh.

  1. connect the raspberry pi to the private port of the router (on MyNet N600, this is the third port from the power button)


  1. login to the router using ssh root@[ip home node] and provide password specified when flashing/ configuring the home node. This should look something like:
$ ssh root@100.65.xx.xx
root@100.65.xx.xx's password: 

BusyBox v1.23.2 (2017-11-21 21:45:39 UTC) built-in shell (ash)

... some banner ...
  1. figure out your static mesh ip addresses. The home node comes with two extra mesh ip addresses. Normally, you'd use them for extender nodes. However, now, we are using one of them for the raspberry pi to get into the mesh. The available static mesh ip addresses are the home node ip address, lets say, with the last number added one and two: and . You can double check this by running the following on the home node:
# cat /etc/config/notdhcpserver 
config server
  option enabled '1'
  list addresses 'eth0.1='
  list addresses 'eth0.2='
  option hook_script '/opt/notdhcpserver/'
  option ssl_cert '/etc/uhttpd.crt'
  option ssl_key '/etc/uhttpd.key'
  option timeout_length '180'

where eth0.1 and eth0.2 contains the two static ip addresses.

  1. after logging into the home node, figure out the ip address of the raspberrypi by running cat /tmp/dhcp.leases producing something like:
root@xx:~# cat /tmp/dhcp.leases 
... [pi ip address] raspberrypi *

The number sequence preceding the raspberrypi word is the (private) ip address given by the router dhcp to the raspberry pi.

  1. ssh into raspberry pi by using sudo pi@[pi ip address] and providing password (default: raspberry)

  2. set static mesh ip address on raspberry pi by sudo nano /etc/dhcpcd.conf and adding section:

interface eth0
static ip_address=
static routers=
static domain_name_servers= 

where ip_address is the static mesh ip, routers is the mesh ip of your home node, and domain_name_servers include the route node ip and the mesh nameserver at .

  1. shutdown your pi by running sudo shutdown now and unplug from the home node private port.

  2. plug pi into the second mesh port (confirmed to work with MyNet N600 that meshes with another home node to get route to internet mesh port), disconnect the power supply and power back on. Note that for some reason, this approach doesn't work with the second mesh node, if this is the case, use the public port, the port next to the yellow colored ethernet port (confirmed to work with MyNet N750 bridge to WAN via hotspot, public-port)

  3. ssh into pi by running ssh pi@[pi mesh ip address] on your laptop or router.

  4. if all works well, the mesh is yours to serve to from your pi.

Use Case - Scuttlebot on RaspberryPi


2 meshing raspberrypi created via previous use case

1 internet access


  1. ssh into raspberry pi

  2. install nvm curl -o- | bash for more up-to-date see nvm install instructions

  3. activate nvm on login by creating a .bash_profile with touch ~/.bash_profile and adding source ~/.bashrc in it.

  4. exit / relogin using ssh

  5. type nvm , which should show:

$ nvm

Node Version Manager
  1. install node /npm using nvm

  2. set default node alias to latest node version

  3. install scuttlebot using up-to-date install instructions, making sure to install linux dependencies

  4. start sbot by sbot server --logging.level=info, you should see something like:

$ sbot server --logging.level=info
scuttlebot 10.5.0 /home/pi/.ssb logging.level:info
my key ID: Y04ZhLf/fYtyk2RejQpVQkQSBzaRspIGjzLnFFkZPZI=.ed25519
  1. repeat process for second raspberry pi

  2. publish a message using something like sbot publish --type post --text "why did I cross the road?" (repeat for other sbot server)

  3. stop sbot

  4. edit ~/.ssb/gossip.json and manually add:

[ { "host" : "[mesh ip address of peer pi]", "port": 8008, "key": "@[key id of peer shown on startup]"} ]
  1. start sbots, and notices messages like:
info @Y04 SBOT 1 peers loaded from /home/pi/.ssb/gossip.json 
  1. now follow each other using sbot publish --type contact --contact "@89LpMgCkzPxAiCaxR0XqcUD2uhbFZCD5rnYvX86vNJM=.ed25519" --following

  2. manually start a replication by sbot replicate.upto

  3. check the logs to see whether peer messages are showing up using sbot log

example message 1

  "key": "%MZKRrGH9gn3v3NSEo27ABDpDxnSQLuDqp2dgiFBHcY0=.sha256",
  "value": {
    "previous": "%OFOrIsC/fC5GA8GstLLaYIh7oCB+TH3rA4hG1Y5qJF0=.sha256",
    "sequence": 4,
    "author": "@89LpMgCkzPxAiCaxR0XqcUD2uhbFZCD5rnYvX86vNJM=.ed25519",
    "timestamp": 1517016198197,
    "hash": "sha256",
    "content": {
      "type": "post",
      "text": "The chicken crossed the road, because it wanted some cream."
    "signature": "flck2NZ3f9FV7Sn++Bex5BcXWOSdnGcylGZ4wSFgNjWyTqjrCQK1L3UMOQp9BcarSVNF4txR3tumSHaezfEzAA==.sig.ed25519"
  "timestamp": 1517016198422

example message 2

  "key": "%QJZjdBl4nxppB9mJJlxxh2yM8wvPKrPWkI56hcKf+oo=.sha256",
  "value": {
    "previous": null,
    "sequence": 1,
    "author": "@Y04ZhLf/fYtyk2RejQpVQkQSBzaRspIGjzLnFFkZPZI=.ed25519",
    "timestamp": 1517014903948,
    "hash": "sha256",
    "content": {
      "type": "post",
      "text": "why did I cross the road?"
    "signature": "DxmD+wSEQDRl1dDn8QvFA8z6RcKhsg/3deB5RLVlUhiept/JJ9aKS0mQe1Usp4237eMsePpN/bdP5xMm2vLxCw==.sig.ed25519"
  "timestamp": 1517014903998