From: ST <smntov@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Interface's Address is not saved when SaveConfig = true in config
Date: Sat, 21 Apr 2018 21:57:29 +0300 [thread overview]
Message-ID: <1524337049.2059.29.camel@gmail.com> (raw)
In-Reply-To: <CAHmME9q_7DK67f=TakrRimX7fs_ZrKQrNP8wHoauj3r7GwRsyQ@mail.gmail.com>
Debian 8 Jessie
iproute2/oldstable,now 3.16.0-2 amd64
On Fri, 2018-04-20 at 21:39 +0000, Jason A. Donenfeld wrote:
> Out of date iproute2?
>
>
> Which distro? Version?
>
> --
> Sent from my telephone.
>
>
> On Fri, Apr 20, 2018, 12:36 ST <smntov@gmail.com> wrote:
>
> Hello,
>
> I have
> ...
> Address = 192.168.4.1/24
> SaveConfig = true
> in wg0.conf
>
> 1. if I add a peer with `wg set wg0 peer ...` WG doesn't add
> it
> immediately to the wg0.conf file, only after I run `wg-quick
> down wg0`.
> Why not? What happens if the system crashes unexpectedly?...
> The peer
> will not be saved to the config file and the information will
> be lost.
>
>
> 2. once I run `wg-quick down wg0` I get:
>
> Option "-all" is unknown, try "ip -help".
> cat: /etc/resolvconf/run/interface/wg0: No such file or
> directory
> [#] wg showconf wg0
> sync: ignoring all arguments
> [#] ip link delete dev wg0
>
> Now the wg0.conf is enhanced with the peer details that was
> added
> through command line, but the Address = 192.168.4.1/24
> disappears from
> the config. So running `wg-quick up wg0` again doesn't assigns
> IP to the
> wg0 interface... What's wrong?
>
> I'm using version:
> apt list wireguard
> wireguard/unstable,now 0.0.20180304-1 all [installed]
>
> Thank you!
>
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-04-21 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 10:36 Interface's Address is not saved when SaveConfig = true in config ST
2018-04-20 21:39 ` Jason A. Donenfeld
2018-04-21 18:57 ` ST [this message]
2018-04-24 8:59 ` ST
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=1524337049.2059.29.camel@gmail.com \
--to=smntov@gmail.com \
--cc=Jason@zx2c4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.