From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: ST <smntov@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Interface's Address is not saved when SaveConfig = true in config
Date: Fri, 20 Apr 2018 21:39:12 +0000 [thread overview]
Message-ID: <CAHmME9q_7DK67f=TakrRimX7fs_ZrKQrNP8wHoauj3r7GwRsyQ@mail.gmail.com> (raw)
In-Reply-To: <1524220589.2059.27.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2139 bytes --]
next prev parent reply other threads:[~2018-04-20 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 10:36 ST
2018-04-20 21:39 ` Jason A. Donenfeld [this message]
2018-04-21 18:57 ` ST
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='CAHmME9q_7DK67f=TakrRimX7fs_ZrKQrNP8wHoauj3r7GwRsyQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=smntov@gmail.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).