From: "Igor Martinovski" <igor@ownmail.net>
To: wireguard@lists.zx2c4.com
Subject: Feature Request: Add "include" directive to config file
Date: Thu, 25 Jul 2019 18:38:16 -0400 [thread overview]
Message-ID: <beaf5d99-cca4-4980-a1d8-ba0444117a4a@www.fastmail.com> (raw)
It would be nice if the config parser could support an include directive such that each peer configuration can be kept in a separate file.
This would allow easier management of a large number of peers. It would also serve as a way of having a friendly name for each peer or peers by the file name.
Sample below:
[Interface]
Address = 10.22.22.2/24
PrivateKey = ...
[Peer]
PublicKey =...
AllowedIPs = 0.0.0.0/0
Endpoint = ...
# append a config file
include='/usr/local/etc/wireguard/family.conf'
# include all files in this directory
include='/usr/local/etc/wireguard/friends/'
--
Igor M.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-08-25 15:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=beaf5d99-cca4-4980-a1d8-ba0444117a4a@www.fastmail.com \
--to=igor@ownmail.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).