Skip to content

Installation Guide

Automated Repository Setup

The bootstrap script detects your Linux distribution, imports the repository GPG signing key, and configures the package source:

curl -fsSL https://repo.ololo.tech/setup.sh | sudo sh

Then install the components you need:

# Server (mesh relay node)
sudo apt install ololo-relay      # Debian / Ubuntu
sudo dnf install ololo-relay      # Fedora / RedOS

# Desktop admin client (GUI) — from the same repository
sudo apt install ololo-relay-admin
sudo dnf install ololo-relay-admin

The systemd service does not start automatically upon package installation — /etc/ololo-relay/node.yaml ships with a node.id: REPLACE_ME placeholder that must be configured before first boot. This is intentional so the service never enters a crash-loop before minimal setup:

sudo $EDITOR /etc/ololo-relay/node.yaml
sudo systemctl enable --now ololo-relay
sudo journalctl -u ololo-relay -f

For automated multi-host provisioning without interactive configuration, see Headless Ansible Deployment.

Manual Installation (Debian / Ubuntu)

sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://repo.ololo.tech/pubkey.asc \
  | sudo gpg --dearmor -o /etc/apt/keyrings/ololo-relay.gpg

echo "deb [signed-by=/etc/apt/keyrings/ololo-relay.gpg] \
https://repo.ololo.tech/apt stable main" \
  | sudo tee /etc/apt/sources.list.d/ololo-relay.list

sudo apt update
sudo apt install ololo-relay

Verify the imported key fingerprint:

gpg --show-keys /etc/apt/keyrings/ololo-relay.gpg

Compare the fingerprint against the value published on the Security page.

Manual Installation (Fedora / RedOS)

sudo rpm --import https://repo.ololo.tech/pubkey.asc

sudo tee /etc/yum.repos.d/ololo-relay.repo <<'EOF'
[ololo-relay]
name=ololo-relay
baseurl=https://repo.ololo.tech/rpm
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://repo.ololo.tech/pubkey.asc
EOF

sudo dnf install ololo-relay

RedOS Murom Notes

  • SELinux is enabled in enforcing mode by default. Standard paths (/usr/bin/, /lib/systemd/system/, /var/lib/) work out of the box. If binding to a non-standard TCP port:

    sudo semanage port -a -t http_port_t -p tcp <port>
    
  • No FSTEC certification. The package is distributed as uncertified application software. Deployment in regulated environments that mandate certified security appliances is solely at the administrator’s discretion.

Rollback & Removal

The server package ololo-relay and desktop GUI ololo-relay-admin share synchronized version numbers (for example 0.9.21):

sudo apt install ololo-relay=0.9.20           # pin version (Debian/Ubuntu)
sudo dnf downgrade ololo-relay-0.9.20-1       # pin version (Fedora/RedOS)

sudo apt remove ololo-relay                   # remove binary, keep config & state
sudo apt purge  ololo-relay                   # remove config too (state remains)
sudo dnf remove ololo-relay

The ololo-relay system user and /var/lib/ololo-relay/ state directory are intentionally preserved across package removals so remove+install upgrades never wipe cluster state. Delete them manually if decommissioning a host permanently.

Gateway Routing & Interface Capture

If the node acts as a network gateway capturing traffic from a LAN or VPN interface (capture_iifs, capture_wan_iface, capture_exclude_dst, fail_closed), see the dedicated Routing section.

Upgrades

apt and dnf pull new releases through standard system upgrades:

sudo apt update && sudo apt upgrade ololo-relay ololo-relay-admin
sudo dnf upgrade ololo-relay ololo-relay-admin

With unattended-upgrades (Debian/Ubuntu) or dnf-automatic (Fedora / RedOS), updates apply on schedule. During restarts, the service drains active sessions within shutdown.drain_timeout (30s by default); to reload renewed TLS certificates with zero connection drops, run systemctl reload ololo-relay (SIGHUP).