From: Samuel Holland <samuel@sholland.org>
To: "Rene 'Renne' Bartsch, B.Sc. Informatics" <ml@bartschnet.de>,
wireguard@lists.zx2c4.com
Subject: Re: wg-quick: Separate files for interface and peer definitions?
Date: Thu, 27 Dec 2018 13:06:53 -0600 [thread overview]
Message-ID: <fbeed46d-2011-68a5-a932-8a9348a4d9ca@sholland.org> (raw)
In-Reply-To: <5c712311-26d6-f2e2-d941-aec6881b67e9@bartschnet.de>
On 12/27/18 10:19, Rene 'Renne' Bartsch, B.Sc. Informatics wrote:
> we want to distribute the same file with peer definitions to all Wireguard
> peers.
>
> Is there any way in wg-quick to use one configuration file for the interface
> definition and another file for the definition of peers?
In a way, yes. You can call `wg addconf` from a wg-quick PostUp hook to include
another configuration file containing only peers. However, the recommended way
of doing this if you are using a configuration management system
(puppet/ansible/salt/etc.) is to use a template that will concatenate the
interface configuration and peer definitions into one file.
Note that WireGuard will ignore a peer whose public key matches the interface's
private key. So you can distribute a single list of peers everywhere. Only the
[Interface] section needs to be customized per machine.
Hope that helps,
Samuel
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2018-12-27 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 16:19 wg-quick: Separate files for interface and peer definitions? Rene 'Renne' Bartsch, B.Sc. Informatics
2018-12-27 19:06 ` Samuel Holland [this message]
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=fbeed46d-2011-68a5-a932-8a9348a4d9ca@sholland.org \
--to=samuel@sholland.org \
--cc=ml@bartschnet.de \
--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).