From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 765881FF0AF for ; Fri, 20 Nov 2026 17:00:50 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id CA76721771; Fri, 20 Nov 2026 17:00:38 +0100 (CET) From: Stefan Hanreich To: pve-devel@lists.proxmox.com Subject: [PATCH pve-manager 06/10] ui: sdn: fabrics: wireguard: show persistent keepalive of neighbors Date: Fri, 20 Nov 2026 17:00:21 +0100 Message-ID: <20261120160026.512565-7-s.hanreich@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261120160026.512565-1-s.hanreich@proxmox.com> References: <20261120160026.512565-1-s.hanreich@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1795190433318 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.209 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: RTZFK2RLQSSQ3VSK4EKGYT6MTI5LUJ4P X-Message-ID-Hash: RTZFK2RLQSSQ3VSK4EKGYT6MTI5LUJ4P X-MailFrom: s.hanreich@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: The neighbor status reports a peer as down only if persistent keepalive is enabled for it, so show the interval that WireGuard currently uses for each peer. This also makes it visible if the running interval differs from the configured one, e.g. because applying the configuration failed. Signed-off-by: Stefan Hanreich --- www/manager6/sdn/FabricsContentView.js | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/www/manager6/sdn/FabricsContentView.js b/www/manager6/sdn/FabricsContentView.js index bbe4b77e..2c83a0f1 100644 --- a/www/manager6/sdn/FabricsContentView.js +++ b/www/manager6/sdn/FabricsContentView.js @@ -88,6 +88,14 @@ Ext.define('PVE.sdn.FabricNeighborsContentView', { return Proxmox.Utils.render_timestamp(value); }, }, + { + // TRANSLATORS: 's' is the SI abbreviation for seconds, the unit of the value + header: gettext('Persistent Keepalive') + ' (s)', + sortable: true, + dataIndex: 'persistent-keepalive', + flex: 0.5, + renderer: (value) => value ?? gettext('off'), + }, { header: gettext('Bytes transmitted'), sortable: true, -- 2.47.3