What are the options for stopping and starting?
aaronmdjones at gmail.com
Mon Dec 4 18:00:12 CET 2017
-----BEGIN PGP SIGNED MESSAGE-----
On 04/12/17 16:01, Whit Blauvelt wrote:
> Great design on this project. If I can understand some of the
> things the docs don't cover yet, I'll try to write them up.
> The first thing I'm tripping over is the relationship of a
> configuration file, say wg0.conf, to the wg kernel module. I can
> follow the documented examples to get a connection set up; but once
> it's going I'm vague on how to reset it to other values -- perhaps
> another port, or different allowed IPs
wg(8) can dynamically adjust the configuration of an interface -- either
directly on the command-line, or by using 'addconf' or 'setconf' and
giving a (new) configuration file. The former won't erase any existing
configuration that doesn't exist in the new file.
> .... There are some cases where hand-editing of the conf file gets
> overwritten by some automated process. Does that have something to
> do with the "SaveConfig" flag? What's the theory there?
Interface configuration can be persisted to the configuration file and
restored when the interface is next brought up. This is useful in the
context of dynamic configuration; some other service may have adjusted
your configuration, added or removed peers, etc, and you want this
preserved. That's what the flag you mentioned does.
> More centrally, how does one apply changes through the conf file?
> Most of use are used to user-space daemons, where restarting the
> daemon or having it reload its prefs is standard.
# wg addconf wg0 /etc/wireguard/wg0.conf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the WireGuard