SUMMARY I've got a WireGuard profile, when I add a `Persistent Keepalive` to a peer via the the applet, press apply. The setting doesn't actually apply, if you reopen the applet then the connection, the field is then blank again. You don't need to connect with the profile, just try setting it and then close the applet window and then go back in to check it's applied. If you set the `persistent-keepalive` directly in the .connection file and reload network manager. It'll then show in the NetworkManager Applet, but making any changes to the connection to the peers list will cause the `persistent-keepalive` to be unset once again using the applet. STEPS TO REPRODUCE 1. Open WireGuard connection profile in nm-applet 2. Go to the `WireGuard Interface` tab 3. Click `peers` 4. Add value like `25` to `Persistent Keepalive` 5. Click `OK` to the `Peer Properties` window 6. Click `Ok` to the `Connections- System Settings` window 7. Open WireGuard connection profile in nm-applet 8. Go to the `WireGuard Interface` tab 9. Click `peers` 10. See value wasn't applied. OBSERVED RESULT `persistent-keepalive` isn't set EXPECTED RESULT `persistent-keepalive` should be set to defined value SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 36 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION System is fully up to date, as of writing this bug.
Thank you for the bug report! Please note that Plasma 5.25.5 is not supported for much longer by KDE; supported versions are 5.24, and 5.26 or newer. If at all possible please upgrade to a supported version and verify that the bug is still happening there. If you're unsure how to do this, contact your distributor about it.
Also happens on Fedora 37 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 37 KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6
Bug exists on Ubuntu 20.04.5 LTS with KDE plasma version 5.18.8. Note: adding "persistent-keepalive=25" under the [wireguard-peer. ...] heading in /etc/NetworkManager/system-connections/<wg.nmconnection> does not fix the issue for me. i.e. I cannot establish a functional wireguard tunnel this way. However, `sudo wg-quick up </etc/wireguard/wg_conf_file_name>` (which has PersistentKeepAlive = 25 under the [Peer] heading does create a functional wireguard tunnel.
I am running 5.26.5-0xneon+22.04+jammy+release+build17 and this bugs still exists.
@sn: I added "persistent-keepalive=21" to the [wireguard-peer.xxxxx] section and ran `nmcli connection reload`. Restarted conenction via plasma applet, and `wg show` now showed the keep alive value.