From: John Accoun <jsonacc@gmail.com>
To: Steve Gilberd <steve@erayd.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: how would one go about building an admin frontend?
Date: Sun, 13 Jan 2019 01:09:59 +0100 [thread overview]
Message-ID: <CALLpx3SftnnHC6pNPp=gGMi0OZBJ6F849KT-VF28aGfgD2naqA@mail.gmail.com> (raw)
In-Reply-To: <CAJQSx3ZqE99QnZx8O2M9J-VFP=V=We3Zbp7iNQnnO5ptNf8ocQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2144 bytes --]
> Why not use an existing solution (e.g. puppet et al)? The capability is
already there,
No. It's not. Notice that I did mention that the devices would call a
server to register themselves. In fact, the whole problem I am trying to
solve is providing connectivity to peers behind NATs and connected from
unknown locations. Being able to just ssh'ing into a peer is the end goal
itself, not the starting point.
But let's please not get off topic. I think I was clear in what I asked.
On Fri, Jan 11, 2019 at 12:17 PM Steve Gilberd <steve@erayd.net> wrote:
> Why not use an existing solution (e.g. puppet et al)? The capability is
> already there, unless you need a GUI.
>
> Cheers,
> Steve
>
> On Fri, 11 Jan 2019, 21:09 John Accoun, <jsonacc@gmail.com> wrote:
>
>> 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?
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
> --
>
> Cheers,
>
> *Steve Gilberd*
> Erayd LTD *·* Consultant
> *Phone: +64 4 974-4229 **·** Mob: +64 27 565-3237*
> *PO Box 10019, The Terrace, Wellington 6143, NZ*
>
[-- Attachment #1.2: Type: text/html, Size: 3403 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-01-16 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 0:14 how would one go about building an admin frontend? John Accoun
2019-01-11 11:17 ` Steve Gilberd
2019-01-13 0:09 ` John Accoun [this message]
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='CALLpx3SftnnHC6pNPp=gGMi0OZBJ6F849KT-VF28aGfgD2naqA@mail.gmail.com' \
--to=jsonacc@gmail.com \
--cc=steve@erayd.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).