Thanks for the recent changes I am now a Patreon contributor and have access to the LTS release images.
Currently running a rolling release that is working fine and wanted to see how the LTS version differed in terms of day to day performance.
Hit a small snag with my working wireguard config. The syntax has changed which is mostly fine, however in my current config I use the private-key attribute to point to a generated key set stored in /config/auth/wireguard/wg[x]
This does not seem to have an equivalent in 1.2.5.
you are right, the CLI from 1.2 and 1.3 differ in a lot of ways. As we provide an upgrade path from 1.2 to 1.3 through a bunch of migration scripts which rewrite the config on first boot under the hood, we do not supply “downgrade” conversion scripts.
In your special case the CLI syntax has changed in VyOS 1.2 from
set interfaces wireguard wg0 peer foo endpoint 1.1.1.1:2222
to a more “frindly” version in 1.3
set interfaces wireguard wg0 peer foo address 1.1.1.1 set interfaces wireguard wg0 peer foo port 2222
I should have made it clearer in my question. I already changed the syntax to the older format as you mentioned.
However, I cannot find a way to specify the private-key attribute. When trying to save the config the commit fails as a private-key cannot be found even though it is there under /config/auth/wireguard/wg0/private.key
Tunnel 1 : Route via a mullvad endpoint
Tunnel 2 : wg “server” that routes via the native ISP for remote LAN and WAN access
Tunnel 3 : wg “server” that routes via the mullvad endpoint for remote LAN access and VPN WAN access
Am I right in presuming the multi-key support isn’t targeted for crux?
I use the rolling iso as much as possible to weed out bugs and testing, somif possible, go woth 1.3 to help us make it more stable, the more tester the sooner there will be a 1.3 stable release.