Bug #11288
closed
Wireguard: Peer PSK is auto-filled to the keepalive field
100%
Description
If you configure a PSK on a WireGuard peer and then edit that peer the keep-alive field will be populated by the PSK value.
Updating that peer and saving obviously produces a non loadable conf file:
Jan 22 15:14:33 php-fpm 26466 /vpn_wg_edit.php: The command '/usr/local/bin/wg setconf 'wg0' '/etc/wg/wg0.conf'' returned exit code '1', the output was 'Persistent keepalive interval is neither 0/off nor 1-65535: `gzU4Ry5WXrqPhdFR8YsFg5z/PrnbxDwZLrbh7aK7Xow=' Configuration parsing error'
Tested:
21.02-DEVELOPMENT (amd64) built on Thu Jan 21 00:08:27 EST 2021 FreeBSD 12.2-STABLE
Updated by Viktor Gurov almost 4 years ago
Updated by Jim Pingle almost 4 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 262dba240a74a4b70cacbe6835dcef344d44f316.
Updated by Viktor Gurov almost 4 years ago
- Status changed from Feedback to Resolved
2.5.0.a.20210122.2350 fixed
Updated by Christian McDonald almost 4 years ago
I'm still having issues with the Keepalive field. When I edit and peer and set the keepalive value, save and come back the field is blank. The value is also not present in 'wg showconf' at the shell.
Updated by Jim Pingle almost 4 years ago
- Status changed from Resolved to Feedback
I found a typo in the variable name used to populate the value in the GUI, but the backend appears to be using it appropriately. Commit coming momentarily.
I'm not sure if wg is supposed to print that value or not, but it does appear in the configuration in /etc/wg/
Updated by Christian McDonald almost 4 years ago
tested on gitsync yesterday and today via normal snapshot upgrade, both look good here.
Updated by Jim Pingle almost 4 years ago
- Status changed from Feedback to Resolved