All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Accoun <jsonacc@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: how would one go about building an admin frontend?
Date: Fri, 11 Jan 2019 01:14:30 +0100	[thread overview]
Message-ID: <CALLpx3RrfNM7Brf0m-9eEMbRiHneUWK00fNorUAn948asC6jSg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 938 bytes --]

I need to provision a large number of linux devices on multiple locations
and put them all on a VPN.
Configuring each device manually is too tedious. I was thinking of spinning
up a server with a small HTTP api to exchange keys and configure wireguard
on both sides. Then each device would call this server to register itself.
And while I am a it I thought I could throw together a minimal admin ui
that I could use for example to manually remove peers.

I red the 'Web App provisioning Server' which I believe describes a
possible solution for this use case. But I am confused with the whole data
storage thing. Where do configuarations live? Are the configuration files
at /etc/whireguard/ the source of truth? If I edit these when is the list
of peers refreshed?

The above mentioned document suggests shelling out to command line tools.
Is this the recommended way. Does a general purpose library for managing
wireguard config exist?

[-- Attachment #1.2: Type: text/html, Size: 1026 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2019-01-11  8:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11  0:14 John Accoun [this message]
2019-01-11 11:17 ` how would one go about building an admin frontend? Steve Gilberd
2019-01-13  0:09   ` John Accoun
2019-01-16 20:25 ` Tharre
2019-01-21 18:40   ` Vincent Wiemann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALLpx3RrfNM7Brf0m-9eEMbRiHneUWK00fNorUAn948asC6jSg@mail.gmail.com \
    --to=jsonacc@gmail.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.