From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [PATCH docs/manager/network/proxmox{,-ve-rs,-perl-rs} v2 00/11] Status reporting for WireGuard fabrics
Date: Fri, 20 Nov 2026 08:42:42 +0100 [thread overview]
Message-ID: <179515721888.2281522.2289450685312416283.b4-ty@b4> (raw)
In-Reply-To: <20261117183500.750636-1-s.hanreich@proxmox.com>
On Tue, 17 Nov 2026 19:34:47 +0100, Stefan Hanreich wrote:
> ## Introduction
>
> This patch series adds status reporting for WireGuard fabrics to pvestatd and
> exposes additional information about WireGuard interfaces and neighbors (=
> peers) via the pre-existing interface/neighbors endpoints for fabrics.
>
>
> [...]
Applied, thanks!
Tested on a three-node cluster: the status, interfaces and neighbors all
look as expected, including idle neighbors without keepalive.
What I changed in your patches: parse errors now name the command whose
output failed to parse, and a listen port of 0, where the kernel picks
the port, no longer marks the interface as broken. The rest is docs and
wording.
Still open:
- On a node outside the WireGuard fabric, the neighbors and interfaces
views return an error instead of an empty list, as OpenFabric and OSPF
do.
- For an interface without a private key, the interfaces view shows the
configured key, even though the overall status correctly says it's
broken.
- Refreshing the views and a keepalive column could come later.
[proxmox]
[01/11] network-api: add missing getters
commit: 48addd495e6be64f9ccfbe50f01ea9a2057c1ad0
[02/11] network-api: add support for parsing interface flags
commit: cbceee640c0d78c76928edaf92f7f3667c4dc087
[03/11] wireguard: derive additional traits for public key
commit: e83e610a526a9a01069a7716313664fb0034989e
[proxmox-perl-rs]
[06/11] sdn status: fabrics: add status reporting for wireguard
commit: bd6b3d4a8ccb7b0ef8edb0ffd26e2d8f92ae0b5c
[07/11] sdn status: fabrics: check interfaces and peers for wireguard status
commit: fdc296c13660d459164f12d53900a81fe0b17a59
[08/11] sdn status: fabrics: report status of wireguard neighbors
commit: 57788ed63038094cc36c9f195e7497a67bfc63f7
[proxmox-ve-rs]
[04/11] ve-config: sdn: wireguard: add getters for interface listen port and public key
commit: 73586aa47e1831a72694ab036f9b177cf3d4bc5d
[05/11] ve-config: sdn: wireguard: add helper for resolving the peers of an interface
commit: 757c52622db3249b15af524bd3fe1b361afd9296
[pve-docs]
[11/11] sdn: add documentation for wireguard status reporting
commit: 636b5ecdf7774aabbd68ea1e01ae616f0bbf4fba
[pve-manager]
[10/11] ui: fabric content: add wireguard protocol
commit: fe6606448e45333507c17131fb5901d74b84470e
[pve-network]
[09/11] api: fabric status: add schema for wireguard properties
commit: 9cc6d62db3dc369138259caa1326b751edc59767
prev parent reply other threads:[~2026-11-20 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 18:34 [PATCH docs/manager/network/proxmox{,-ve-rs,-perl-rs} v2 00/11] Status reporting for WireGuard fabrics Stefan Hanreich
2026-11-17 18:34 ` [PATCH proxmox v2 01/11] network-api: add missing getters Stefan Hanreich
2026-11-17 18:34 ` [PATCH proxmox v2 02/11] network-api: add support for parsing interface flags Stefan Hanreich
2026-11-17 18:34 ` [PATCH proxmox v2 03/11] wireguard: derive additional traits for public key Stefan Hanreich
2026-11-17 18:34 ` [PATCH proxmox-ve-rs v2 04/11] ve-config: sdn: wireguard: add getters for interface listen port and " Stefan Hanreich
2026-11-17 18:34 ` [PATCH proxmox-ve-rs v2 05/11] ve-config: sdn: wireguard: add helper for resolving the peers of an interface Stefan Hanreich
2026-11-17 18:34 ` [PATCH proxmox-perl-rs v2 06/11] sdn status: fabrics: add status reporting for wireguard Stefan Hanreich
2026-11-17 18:34 ` [PATCH proxmox-perl-rs v2 07/11] sdn status: fabrics: check interfaces and peers for wireguard status Stefan Hanreich
2026-11-17 18:34 ` [PATCH proxmox-perl-rs v2 08/11] sdn status: fabrics: report status of wireguard neighbors Stefan Hanreich
2026-11-17 18:34 ` [PATCH pve-network v2 09/11] api: fabric status: add schema for wireguard properties Stefan Hanreich
2026-11-17 18:34 ` [PATCH pve-manager v2 10/11] ui: fabric content: add wireguard protocol Stefan Hanreich
2026-11-17 18:34 ` [PATCH pve-docs v2 11/11] sdn: add documentation for wireguard status reporting Stefan Hanreich
2026-11-18 15:20 ` [PATCH docs/manager/network/proxmox{,-ve-rs,-perl-rs} v2 00/11] Status reporting for WireGuard fabrics Arthur Bied-Charreton
2026-11-20 7:42 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179515721888.2281522.2289450685312416283.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.