Set PersistentKeepAlive for the PiRogue-side WireGuard peer (“server”…

…) as well. Link: #13
PiRogueToolSuite · Aug 24, 2024 · 667d8ef · 667d8ef
1 parent 9c6abaf
commit 667d8ef
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/pirogue-admin/debian/changelog b/pirogue-admin/debian/changelog
@@ -1,3 +1,10 @@
+pirogue-admin (1.2.3) UNRELEASED; urgency=medium
+
+  * Set PersistentKeepAlive for the PiRogue-side WireGuard peer (“server”)
+    as well (https://github.com/PiRogueToolSuite/pirogue-admin/issues/13).
+
+ -- Cyril Brulebois <cyril@debamax.com>  Sat, 24 Aug 2024 23:58:49 +0200
+
 pirogue-admin (1.2.2) bookworm; urgency=medium
 
   * Bridge the gap between both CLI tools:

diff --git a/pirogue-admin/pirogue_admin/system_config/wireguard.py b/pirogue-admin/pirogue_admin/system_config/wireguard.py
@@ -301,6 +301,7 @@ def deploy_config(self):
             lines.append(f'PublicKey = {peer.public_key}')
             # IPv4/IPv6: /32
             lines.append(f'AllowedIPs = {peer.get_ipv4_address(self.config.isolated_network)}/32')
+            lines.append(f'PersistentKeepAlive = {DEFAULT_WG_PERSISTENT_KEEP_ALIVE}')
 
         # Atomic write:
         with wg_conf.with_suffix('.new') as new_wg_conf: