wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Raffaele Spazzoli <rspazzol@redhat.com>
To: "M. Dietrich" <mdt@emdete.de>
Cc: wireguard@lists.zx2c4.com
Subject: Re: dynamic reload of configuration file
Date: Mon, 18 Feb 2019 08:51:38 -0500	[thread overview]
Message-ID: <CACOeLqLEo2mX3AXvEPcG6EAOdwQf+PW3BvfKvYFPzsu6vLp5GQ@mail.gmail.com> (raw)
In-Reply-To: <1550417524.ondhfeso9t.astroid@morple.none>


[-- Attachment #1.1: Type: text/plain, Size: 1423 bytes --]

Samuel,

I read that section of the docs. it doesn't explain the behavior of those
commands on an already "warm" wireguard device (i.e. while the device is in
up state).

M. Dietrich,

the add conf may work when adding a node, but I also need something when
removing a node of the mesh.

two questions:
1. If initialize a wireguard device with a configuration file and then
update the file will the configuration be updated?
2. if I run the set-conf command on an already initialized wiredguard
device, will the configuration be updated without losing the current (and
still existing after the new configuration) connections?

Thanks,
Raffaele

Raffaele Spazzoli
Senior Architect - OpenShift <https://www.openshift.com>, Containers
and PaaS Practice <https://www.redhat.com/en/services/consulting/paas>
Tel: +1 216-258-7717




On Sun, Feb 17, 2019 at 12:38 PM M. Dietrich <mdt@emdete.de> wrote:

> Quotation from Raffaele Spazzoli at Februar 17, 2019 16:21:
> > I'm using wireguard to build a VPN mesh. The nodes of the mesh are
> dynamic
> > and can come and go at any time. Is there a way to reconfigure a
> wireguard
> > device without restarting it or losing the current connections?
>
> yes.
>
> > If yes, how can it be done?
>
> other way around: configure wireguard with the `wg` command
> and  that is persisted to the configuration file.
>
> on restart the file is read and your config applied.
>
> M. Dietrich
>

[-- Attachment #1.2: Type: text/html, Size: 2343 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-02-18 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 15:21 dynamic reload of configuration file Raffaele Spazzoli
2019-02-17 17:22 ` Samuel Holland
2019-02-17 17:31 ` M. Dietrich
2019-02-18 13:51   ` Raffaele Spazzoli [this message]
2019-02-18 14:56     ` Lonnie Abelbeck

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=CACOeLqLEo2mX3AXvEPcG6EAOdwQf+PW3BvfKvYFPzsu6vLp5GQ@mail.gmail.com \
    --to=rspazzol@redhat.com \
    --cc=mdt@emdete.de \
    --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).