What are the options for stopping and starting?
whit at transpect.com
Mon Dec 4 18:29:37 CET 2017
Thanks for the quick response. I've read through that man page several
times. Questions remain.
So "setconf <interface> <configuration-filename>" is the basic equivalent of
"service reload" or the like. Okay.
Is there a preferred way to take WireGuard fully down? We could unload the
wireguard (and ip6_udp_tunnel and udp_tunnel?) modules. But that seems a
crude method. What's perferred? I see we can "set <interface> remove", but
is there a simple command to take them all down? (One could obviously be
scripted; just wondering if I'm missing that one's already there.)
Also, what's "SaveConfig" about? I see I got that from wg-quick:
https://git.zx2c4.com/WireGuard/about/src/tools/wg-quick.8. I see now in
testing that that line's not accepted by wg once it's in the conf file --
nor is the Address line that shows up with wg-quick. I don't see where the
docs are clear that wg-quick and wg can't work from the same conf files.
I'm not complaining. Just trying to help get clarity for myself and others.
Your man pages are well written. But I'm sure you know there's much more to
say. My impression so far is that wg-quick probably shouldn't be used at all
outside of a specific road-warrior situation. Is that correct?
I'm also trying to fully understand the "kill switch" discussion in the
wg-quick man page. Is it the case, given standard use of wg (without
wg-quick), that its wg interfaces are available for unencyrpted traffic just
if wg itself isn't actively sitting on them? Or is this vulnerabilty
specific to wg-quick usage?
On Mon, Dec 04, 2017 at 05:14:01PM +0100, Jason A. Donenfeld wrote:
> Hi Whit,
> See the man page of wg(8):
> $ man 8 wg
> For your convenience it can be found online here:
More information about the WireGuard