Re: Interface's Address is not saved when SaveConfig = true in config

Debian 8 Jessie iproute2/oldstable,now 3.16.0-2 amd64 1. So is the iproute2 version out of date? 2. Is the issue with not saving new peers to the config file immediately as they are add but rather only on `wg-quick down wg0` related to the version being out of date? 3. How are you going to

Re: Interface's Address is not saved when SaveConfig = true in config

Debian 8 Jessie iproute2/oldstable,now 3.16.0-2 amd64 On Fri, 2018-04-20 at 21:39 +, Jason A. Donenfeld wrote: > Out of date iproute2? > > > Which distro? Version? > > -- > Sent from my telephone. > > > On Fri, Apr 20, 2018, 12:36 ST wrote: > > Hello, >

Re: Interface's Address is not saved when SaveConfig = true in config

Out of date iproute2? Which distro? Version? -- Sent from my telephone. On Fri, Apr 20, 2018, 12:36 ST 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 >

Interface's Address is not saved when SaveConfig = true in config

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