From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: applied: [PATCH pve-docs 1/1] sdn: fabrics: wireguard: add simple example
Date: Tue, 26 May 2026 19:57:47 +0200 [thread overview]
Message-ID: <177981826395.2745834.16754802586243858290.b4-ty@b4> (raw)
In-Reply-To: <20260526142237.370426-1-s.hanreich@proxmox.com>
On Tue, 26 May 2026 16:22:35 +0200, Stefan Hanreich wrote:
> Initial feedback has shown that the UI currently is a bit confusing as
> to which field expects which value. Provide a step-by-step setup guide
> for a concrete example setup that should cover most basic uses cases.
> This should help users with setting up WireGuard. In the future, we
> should provide some kind of wizard or auto-full-meshify feature in
> order to automate this procedure.
>
> [...]
Applied, thanks!
Pulled the screenshots from the staff repo but missed re-ordering the commits.
[1/1] sdn: fabrics: wireguard: add simple example
commit: ea70b507a1964f178718a82de72f5ae435ee76d9
prev parent reply other threads:[~2026-05-26 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 14:22 [PATCH pve-docs 1/1] sdn: fabrics: wireguard: add simple example Stefan Hanreich
2026-05-26 17:57 ` 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=177981826395.2745834.16754802586243858290.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox