- 01
Cloud and site
Install Vimify Edge 0.3
Install Edge on the site’s Linux gateway and complete the normal RADIUS setup first. The hotspot must work locally before the optional VPN is added. - 02
VPN hub VPS
Create the management hub
Use a dedicated Ubuntu or Debian VPS. The installer creates the hub key locally and prints only its public key. Open UDP 51820 in the VPS firewall.Hub terminalDownload hubcurl -fL https://vimify.ug/downloads/vimify-vpn-hub-0.1.0.tar.gz -o vimify-vpn-hub.tar.gz mkdir -p vimify-vpn-hub tar -xzf vimify-vpn-hub.tar.gz -C vimify-vpn-hub cd vimify-vpn-hub sudo ./install-hub.sh - 03
Site Edge gateway
Generate the site tunnel locally
Give every site a unique tunnel address. The site private key never leaves the gateway, and only the management VPN range is routed into the tunnel.Site terminalUnique address requiredsudo VIMIFY_VPN_HUB_ENDPOINT="vpn.example.com:51820" \ VIMIFY_VPN_HUB_PUBLIC_KEY="PASTE_HUB_PUBLIC_KEY" \ VIMIFY_VPN_TUNNEL_ADDRESS="10.77.0.10/32" \ /opt/vimify-edge/install-vpn-peer.sh - 04
VPN hub VPS
Register the site public key
Paste the public key printed by the site installer and use the same unique tunnel address. Repeat these two peer steps for each hotspot.Hub terminalPublic key onlysudo VIMIFY_VPN_SITE_NAME="kla-central" \ VIMIFY_VPN_SITE_PUBLIC_KEY="PASTE_SITE_PUBLIC_KEY" \ VIMIFY_VPN_SITE_ADDRESS="10.77.0.10/32" \ ./add-site-peer.sh
Production rules
Keep the tunnel narrow
The supplied setup deliberately avoids a flat network between hotspots.✓ One keypair and one /32 address per site✓ No default internet route through the VPN✓ No forwarding between site peers✓ No public WinBox, SSH, WebFig or RADIUS✓ Edge authentication continues if the tunnel fails✓ Cloud stores status, never WireGuard private keys
Reference: current MikroTik WireGuard documentation.