{% extends "base.html" %}
{% block content %}
WireGuard mesh Give a laptop or phone its own address inside your network. Warden generates the keys, writes the hub config, and hands you a client file.A private road
home.
Not enabled
Enable WireGuard in warden.yaml to generate a hub, enroll peers, and download ready-to-import client configurations.
mesh: enabled: true interface: wg0 address: 10.44.0.1/24 listen_port: 51820 endpoint: vpn.example.com:51820 config_path: /etc/wireguard/wg0.conf
wg installed and root access.{{ mesh.interface }} is not up yet{% if mesh_status.detail %} — {{ mesh_status.detail }}{% endif %}. Add peers, then press “Apply to host”.| Peer | Address | Endpoint | Handshake | Transfer | Actions |
|---|---|---|---|---|---|
| {{ row.peer.name }} {{ row.peer.public_key[:12] }}… | {{ row.peer.address }} | {{ row.endpoint or '—' }} | {{ row.rx|bytes }} ↓ · {{ row.tx|bytes }} ↑ | ||
| No peers yet. Add a laptop, phone, or a whole subnet. | |||||
{{ hub_public_key }}
“Apply to host” writes {{ mesh.config_path or '/etc/wireguard/' ~ mesh.interface ~ '.conf' }} and runs wg-quick or wg syncconf. Warden must run as root or with CAP_NET_ADMIN to touch the interface.
Peer private keys stay in Warden's SQLite database so you can download a client file again later.