1
1
mirror of https://github.com/vx3r/wg-gen-web.git synced 2024-11-22 02:31:57 +01:00
Simple Web based configuration generator for WireGuard
Go to file
2020-01-31 11:27:30 +09:00
api go fmt / badges 2020-01-30 16:12:26 +09:00
model go fmt / badges 2020-01-30 16:17:29 +09:00
repository go fmt / badges 2020-01-30 16:21:45 +09:00
ui Readme existing conf. Ui parse int 2020-01-31 11:27:30 +09:00
util go fmt / badges 2020-01-30 16:17:29 +09:00
.env Initial commit 2020-01-30 15:45:49 +09:00
.gitignore Initial commit 2020-01-30 15:45:49 +09:00
.gitlab-ci.yml Initial commit 2020-01-30 15:45:49 +09:00
Dockerfile Initial commit 2020-01-30 15:45:49 +09:00
go.mod go fmt / badges 2020-01-30 16:12:26 +09:00
go.sum go fmt / badges 2020-01-30 16:12:26 +09:00
LICENSE-WTFPL Initial commit 2020-01-30 15:45:49 +09:00
main.go Initial commit 2020-01-30 15:45:49 +09:00
README.md Readme existing conf. Ui parse int 2020-01-31 11:27:30 +09:00
Wg-Gen-Web.png Initial commit 2020-01-30 15:45:49 +09:00

Wg Gen Web

Simple Web based configuration generator for WireGuard.


pipeline status Go Report Card Gitlab pipeline status (self-hosted) License: WTFPL GitHub last commit Docker Pulls GitHub go.mod Go version GitHub code size in bytes

Whay another one ?

All WireGuard UI implementations are trying to manage the service by applying configurations and creating network rules. This implementation only generate configuration and its up to you to create network rules and apply configuration to WireGuard. For example by monituring generated directory with inotifywait.

The goal is to run Wg Gen Web in a container and WireGuard on host system.

Features

  • Self-serve and web based
  • Automatically select IP from networks chosen for client
  • QR-Code for convenient mobile client configuration
  • Enable / Disable client
  • Generation of wg0.conf after any modification
  • Dockerized
  • Pretty cool look Screenshot

Running

The easiest way to run Wg Gen Web is using the container image

docker run --rm -it -v /tmp/wireguard:/data -p 8080:8080 -e "WG_CONF_DIR=/data" vx3r/wg-gen-web:latest

Docker compose snipped

version: '3.6'
services:
  wg-gen-web:
    image: vx3r/wg-gen-web:latest
    container_name: wg-gen-web
    restart: unless-stopped
    expose:
      - "8080/tcp"
    environment:
      - WG_CONF_DIR=/data
      - WG_INTERFACE_NAME=wg0.conf
    volumes:
      - /mnt/raid-lv-data/docker-persistent-data/wg-gen-web:/data

How to trigger WireGuard on host

Before going further create a symlink from docker mounted volume to /etc/wireguard

ln -s /mnt/raid-lv-data/docker-persistent-data/wg-gen-web /etc/wireguard

Example with systemd

Using systemd.path monitor for directory changes see systemd doc

# /etc/systemd/system/wg-gen-web.path
[Unit]
Description=Watch /etc/wireguard for changes

[Path]
PathModified=/etc/wireguard

[Install]
WantedBy=multi-user.target

This .path will activate unit file with the same name

# /etc/systemd/system/wg-gen-web.service
[Unit]
Description=Restart WireGuard
After=network.target

[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl restart wg-quick@wg0.service

[Install]
WantedBy=multi-user.target

Which will restart WireGuard service

Example with inotifywait

Using whatever init system create a daemon running this script

#!/bin/sh
while inotifywait -e modify -e create /etc/wireguard; do
  wg-quick down wg0
  wg-quick up wg0
done

How to use with existing WireGuard configuration

After first run Wg Gen Web will create server.json in data directory with alla server informations.

Fill free to modify this file in order to use your existing keys

What is out of scope

  • Generation or application of any iptables or nftables rules
  • Application of configuration to WireGuard

TODO

  • Multi-user support behind Authelia (suggestions / thoughts are welcome)
  • Send configs by email to client

License