# Wireguard-Peer-Manager ![image](https://user-images.githubusercontent.com/4666566/117325184-56f7f800-ae45-11eb-9003-b85aadbf5ff0.png) [![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Fhouse-of-vanity%2FWireguard-Peer-Manager.svg?type=shield)](https://app.fossa.com/projects/git%2Bgithub.com%2Fhouse-of-vanity%2FWireguard-Peer-Manager?ref=badge_shield) 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: ```shell # 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 < python3 bot.py ``` ## Config 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. ## Telegram Interface drawing drawing ## License [![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2Fhouse-of-vanity%2FWireguard-Peer-Manager.svg?type=large)](https://app.fossa.com/projects/git%2Bgithub.com%2Fhouse-of-vanity%2FWireguard-Peer-Manager?ref=badge_large)