Adds Wireguard peers to config, reload it and send client config back via Telegram.
FYI: That tool stores client private keys into server config as comments.
How to use:
# create initial wg config or use your own.
# P.S. Keep in mind that WPM can't manage peers created manually
# due to absence of client private key.
$ cd /etc/wireguard
$ git clone https://github.com/house-of-vanity/Wireguard-Peer-Manager wpm
$ cat > wg0.conf <<EOF
[Interface]
Address = 10.150.200.1/24
ListenPort = 51820
PrivateKey = $(wg genkey)
PostUp = iptables -A FORWARD -i %i -o %i -j ACCEPT
PostDown = iptables -D FORWARD -i %i -o %i -j ACCEPT
SaveConfig = false
EOF
$ cd wpm
# install python and system requirements.
$ apt install qrencode python3-pip
$ pip3 install -r requirements.txt
# Create config. It's optionally.
$ cp wpm_example.conf wpm.conf
# CLI usage. Client configs saved into `clients/peer_name.{conf,-qr.png,-qr.txt}`
$ python3 gen.py --peer my-pc # add a new peer `my-pc`
$ python3 gen.py --delete my-pc # delete peer `my-pc`
$ python3 gen.py --update # just regenerate all configs in `clients/`
$ python3 gen.py --json # show WG status in JSON
# Telegram bot usage
$ TG_TOKEN=1292121488:AAG... TG_ADMIN=<comma separated list of usernames> python3 bot.py
| Key | Default | Description |
|---|---|---|
| allowed_ips | 0.0.0.0 | allowed_ips for generated peer configs. |
| dns | 8.8.8.8 | DNS for peer configs |
| hostname | $(hostname -f):51820 | server address for peer configs. May be an IP. |
| config | wg0 | WireGuard config to work with. |
