On Tue, Jan 3, 2017 at 7:46 AM, Daniel Kahn Gillmor <[email protected]> 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 "[email protected]" 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 - ?? _______________________________________________ WireGuard mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/wireguard
