The problem seems to be that if you have IPv6 configuration items in the startup config.boot file, Wireguard gets into an unhappy / broken state after a reboot.
The two config lines causing problems for me are:
set interfaces wireguard wg0 address 2c00:efff:0:8::2/64
and
set interfaces wireguard wg0 peer Y.....................................................= allowed-ips ::/0
When you test the next release, please include IPv6 settings and confirm the VPN survives a reboot.
I closed issue 99 with a hack to add these two lines after a reboot, but it's not ideal because if the web interface saves the running config to startup config, the following reboot will get the device into an unhappy state, because it contains IPv6 config items.
General info
Package version: e50-v2-v1.0.20210606-v1.0.20210424.deb
OS version: 2.0.9-hotfix2
Device: EdgeRouter X 5-Port
Hi, thank you for reporting this issue.
I'll take a look ASAP, however the next release will most likely not include a fix.
Please also note that releases are currently mostly or completely untested.
Hi
Related to issue 99: Config fails at reboot #99
The problem seems to be that if you have IPv6 configuration items in the startup config.boot file, Wireguard gets into an unhappy / broken state after a reboot.
The two config lines causing problems for me are:
set interfaces wireguard wg0 address 2c00:efff:0:8::2/64
and
set interfaces wireguard wg0 peer Y.....................................................= allowed-ips ::/0
When you test the next release, please include IPv6 settings and confirm the VPN survives a reboot.
I closed issue 99 with a hack to add these two lines after a reboot, but it's not ideal because if the web interface saves the running config to startup config, the following reboot will get the device into an unhappy state, because it contains IPv6 config items.
General info Package version: e50-v2-v1.0.20210606-v1.0.20210424.deb OS version: 2.0.9-hotfix2 Device: EdgeRouter X 5-Port