From: Anonymous Anonymous <admin@hda.me>
To: "wireguard" <wireguard@lists.zx2c4.com>, "Jason" <jason@zx2c4.com>
Subject: Re: New contrib/ Utility: wg-config
Date: Fri, 09 Dec 2016 08:29:27 +0100 [thread overview]
Message-ID: <158e27c9da7.122ca5a7e30441.7068723817806019547@hda.me> (raw)
In-Reply-To:
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
Anyway to have env variables in the single config file (without wg wgconf blaming), but not in two files per connection? For ex. make wg wgconf redirect variables from . config file to wg-config to deal with.
Using two files will make wireguard configuration even harder to understand, and this means it presume you need to ask someone who will use your vpn to copy two files instead single configuration file (ovpn style)
I addressed this partly there: https://lists.zx2c4.com/pipermail/wireguard/2016-December/000731.html (just started, without routing)
I can't even imagine machine with 50 connections, thats 100 configuration files (including variables files) and thats will be kind of crazy. And this not the worst example.
I really like idea of single config per connection. And this also will make config easier to import in other software (for example you can import ovpn or config file will openvpn setup in networkmanager).
[-- Attachment #2: Type: text/html, Size: 1208 bytes --]
next reply other threads:[~2016-12-09 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 7:29 Anonymous Anonymous [this message]
2016-12-09 10:46 ` Jason A. Donenfeld
-- strict thread matches above, loose matches on Subject: below --
2016-12-08 16:05 Jason A. Donenfeld
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=158e27c9da7.122ca5a7e30441.7068723817806019547@hda.me \
--to=admin@hda.me \
--cc=jason@zx2c4.com \
--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).