Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit@transpect.com>
To: wireguard@lists.zx2c4.com
Subject: What are the options for stopping and starting?
Date: Mon, 4 Dec 2017 11:01:59 -0500	[thread overview]
Message-ID: <20171204160159.GA27666@black.transpect.com> (raw)

Hi,

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
.... 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?

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. Or for kernel stuff, we're used to using
sysctl.d. Working with settings of a kernel module set through a conf file
like this is not such a regular thing. What should the standard methods be
here?

Thanks,
Whit

             reply	other threads:[~2017-12-04 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 16:01 Whit Blauvelt [this message]
2017-12-04 16:14 ` Jason A. Donenfeld
2017-12-04 17:29   ` Whit Blauvelt
2017-12-04 17:31     ` Aaron Jones
2017-12-04 18:37       ` Whit Blauvelt
2017-12-04 18:49         ` Jason A. Donenfeld
2017-12-04 18:06     ` Jason A. Donenfeld
2017-12-04 19:27       ` Whit Blauvelt
2017-12-04 19:36         ` Jason A. Donenfeld
2017-12-04 17:00 ` Aaron Jones

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=20171204160159.GA27666@black.transpect.com \
    --to=whit@transpect.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).