From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Roman Mamedov <rm.wg@romanrm.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Include directive to support "conf.d/*" and the like
Date: Sat, 14 Apr 2018 03:47:57 +0200 [thread overview]
Message-ID: <CAHmME9q8Vp6GTH3u0Lu21HSoBUny58yfdDUB17yss9sq8wzpyg@mail.gmail.com> (raw)
In-Reply-To: <87y3isxp3w.fsf@fifthhorseman.net>
Hi Roman,
This also came up in another thread I was replying to earlier tonight.
While one way indeed is to have an 'include' directive, it seems
simple enough to just do something like:
$ wg setconf wg0 <(cat /etc/wireguard/mysite.conf.d/*.conf)
And then you can have various fragments in there like:
000-interface.conf
001-peergroupA.conf
001-peergroupB.conf
001-peergroupC.conf
And so forth. Would this be an acceptable solution for you?
Jason
next prev parent reply other threads:[~2018-04-14 1:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 8:02 Roman Mamedov
2018-03-16 8:27 ` Kalin KOZHUHAROV
2018-03-16 10:59 ` Daniel Kahn Gillmor
2018-04-14 1:47 ` Jason A. Donenfeld [this message]
2018-04-14 8:47 ` Roman Mamedov
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=CAHmME9q8Vp6GTH3u0Lu21HSoBUny58yfdDUB17yss9sq8wzpyg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=rm.wg@romanrm.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).