Adding propagation to a Reticulum transport node
reticulumFurther configuring our VPS Reticulum node to act as a propagation node in case clients are more or less offline
Install LXMF
pip3 install lxmf
Run LXMF as a propagation node
lxmd --propagation-node
- Copy the destination hash, you’ll want to use it in your
client.
- In MeshChatX, paste it into Settings -> Preferred Propagation Node
- In Sideband, paste it into Preferences -> LXMF Propagation Node
Add to systemd to start automatically
sudo vi /etc/systemd/system/lxmd.service
Content:
[Unit]
Description=LXMF Propagation Node
After=rnsd.service
[Service]
ExecStart=/usr/local/bin/lxmd --propagation-node
Restart=always
User=root
[Install]
WantedBy=multi-user.target
Enable, start and check the daemon
sudo systemctl daemon-reload
sudo systemctl enable lxmd
sudo systemctl start lxmd
sudo systemctl status lxmd
Testing
Restart your interface(s) or whole client. - For MeshChatX, Enabling or Disabling an Interface will bring up a “Restart interfaces” option at the top of the Interfaces page.
If you have two nodes, turn one off. (In MeshChatX, you can also just disable all interfaces.)
Send a message from the connected node.
The message state should show a clock on MeshChatX to show it’s successfully sent for propagation but is pending final delivery to the intended identity.
Re-enable the interface(s) on MeshChatX (or otherwise reconnect the disconnected client) and queued messages should be delivered.