From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [TOOL] wg-config graduates to src/tools, becomes wg-auto-config
Date: Tue, 3 Jan 2017 07:57:18 +0100 [thread overview]
Message-ID: <CAHmME9pnrjo8QcZs44xuGAwZ9TXDkRri68-LZXamuvw9sgwb5g@mail.gmail.com> (raw)
On Tue, Jan 3, 2017 at 7:46 AM, Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
> debian is unlikely to install this if it is expected to be named with a
> .bash suffix:
That's just the title in the source tree. The make file installs it as
`wg-auto-config`.
> That said, i'm not sure what you want with this. If the ultimate goal
> is to have systemd-style .network files, you should ask for these
> changes in systemd itself. That's likely the cleanest approach. If you
> do this, please post a link here to the systemd github issue or pull
> request. :)
There already is a systemd-networkd pull request. I didn't write the
code for it, and it seems like it could use quite a bit of review, but
I'm pretty sure systemd-networkd .network files are going to happen.
The goal of this tool is just to have something quick&dirty for people
to use for flipping on and off their VPN. And it seems like some
people who don't use systemd-network wanted something easy they could
run from a "wireguard@.service" file.
If you have an objection to shipping this, I could just move it back
into contrib.
> (a) fork and exec ip from wg itself
> when running "wg setconf"
Not an option. wg(8) is intended to only take care of
wireguard-related things, and not overlap with ip(8). It should not be
a network management tool at all. In fact, the ultimate goal is to
fold its functionality into iproute2/ip(8).
> (b) name the wrapper something like
> /usr/bin/wg+ip
That's a decent idea for a name. But it does a _bit_ more than merely
combine the two utilities.
So, it seems like thing to do at this point would be to open this
thread up for bike-shedding over the name. What might we call this
tool to convey what it does?
- wg-helper
- wg-quick-setup
- wg-ezconfig
- wg-wrapper
- wg+ip+magic
- ??
next reply other threads:[~2017-01-03 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 6:57 Jason A. Donenfeld [this message]
2017-01-03 21:10 ` Jason A. Donenfeld
2017-01-04 19:21 ` Jason A. Donenfeld
-- strict thread matches above, loose matches on Subject: below --
2017-01-02 6:48 Anonymous Anonymous
2017-01-02 4:57 Jason A. Donenfeld
2017-01-02 14:49 ` Jason A. Donenfeld
2017-01-02 15:17 ` Jason A. Donenfeld
2017-01-03 6:46 ` Daniel Kahn Gillmor
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=CAHmME9pnrjo8QcZs44xuGAwZ9TXDkRri68-LZXamuvw9sgwb5g@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=dkg@fifthhorseman.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).