Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manage Peers using wg-api #70

Open
friesoft opened this issue Feb 6, 2021 · 3 comments
Open

Manage Peers using wg-api #70

friesoft opened this issue Feb 6, 2021 · 3 comments

Comments

@friesoft
Copy link

friesoft commented Feb 6, 2021

I would like to manage remote wireguard installs without having to copy the wireguard config files there and reloading wg.

wg-api seems to be a perfect fit for this usecase as it allows to create and remove peers using the api. Persistence is ensured using SaveConfig in the wg-quick config.

@vx3r
Copy link
Owner

vx3r commented Feb 7, 2021

i am thinking about rewriting whole project to use wg-api but a couple of things are blocking:

  • all components in docker containers ?
  • how to manage networking rules (nat) ?

@friesoft
Copy link
Author

friesoft commented Feb 7, 2021

Personally I have wg-gen-web running in docker on my Synology nas, wireguard on my rpi4 and wg-api in docker on rpi4.

@h44z
Copy link
Contributor

h44z commented Feb 26, 2021

I would suggest using https://github.com/WireGuard/wgctrl-go directly (that is also what wg-api uses internally), so you do not need an separate container for wg-api. I use it myself in https://github.com/h44z/wg-portal and it works flawlessly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants