From: Roman Mamedov <email@example.com>
To: Quentin Vallin <Quentin.Vallin@anuvu.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Subject: Re: [Question or feature request] Support multiple peer config file using something like /etc/wireguard/conf.d
Date: Tue, 23 Aug 2022 21:20:48 +0500 [thread overview]
Message-ID: <20220823212048.71489733@nvm> (raw)
On Tue, 19 Jul 2022 21:36:57 +0000
Quentin Vallin <Quentin.Vallin@anuvu.com> wrote:
> I'm trying to separate my peer configuration and automate it.
> I know that I can use the post hook PostUp = wg addconf /path/to/my/file
> It would be easier to have a special path were wireguard can merge the config file together, like /etc/wireguard/conf.d/<interface_name>/<files>.conf.
Personally I use my own shell script that concatenates pieces of the config
into a single file and runs wg on that. The same script also then handles
addresses, routes and such.
If you're doing any sort of non-trivial setup, you'd likely have a similar
wrapper on top of WG, and then it is easy to also make your own "conf.d".
prev parent reply other threads:[~2022-08-23 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 21:36 Quentin Vallin
2022-08-23 16:20 ` Roman Mamedov [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).