From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs 1/1] sdn: fabrics: wireguard: update endpoint documentation
Date: Thu, 21 May 2026 15:08:54 +0200 [thread overview]
Message-ID: <20260521130857.373765-1-s.hanreich@proxmox.com> (raw)
The split of the endpoint field into endpoint + port field has been
reverted. Update the documentation to reflect this change as well.
Since this has caused confusion while testing, add explicit examples
on the expected values for internal / external nodes respectively.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
pvesdn.adoc | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/pvesdn.adoc b/pvesdn.adoc
index 8b72283..f584526 100644
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -883,11 +883,12 @@ definitions that can be used across the whole cluster.
.Internal
Endpoint:: This is the IP or hostname that other Proxmox VE nodes should use for
-connecting to this Proxmox VE node. This is used together with the endpoint port
-when configuring this Proxmox VE node as a peer.
-
-Endpoint Port:: This is the UDP port that other Proxmox VE nodes should use for
-connecting to this Proxmox VE node. If unset, it defaults to `51820`.
+connecting to this Proxmox VE node (e.g. `192.0.2.1` / `2001:db8::1`). This is
+used together with the 'Listen Port' configured on the separate interfaces for
+constructing the actual endpoint. For instance, if a node has the IP `192.0.2.1`
+as an 'Endpoint' and an interface `wg0` with 'Listen Port' `51820` configured,
+then other nodes will use `192.0.2.1:51820` as endpoint for connecting to this
+node.
Allowed IPs:: A comma-separated list of CIDRs (for example `198.51.100.0/24`,
or `0.0.0.0/0` to tunnel all IPv4 traffic). When selecting this node as a peer
@@ -901,11 +902,10 @@ Name:: The name of the external node.
Public Key:: The public key used by the external node.
-Endpoint:: The IP or hostname that other nodes use to connect to this external
-peer.
-
-Endpoint Port:: The UDP port that other nodes use to connect to this external
-peer. If unset, it defaults to `51820`.
+Endpoint:: The IP or hostname together with the port that other nodes use to
+connect to this external peer (e.g. `192.0.2.1:51820`). If an endpoint uses an
+IPv6 address, then the address needs to be enclosed in square brackets (e.g.
+`[2001:db8::1]:51820`).
Allowed IPs:: A comma-separated list of CIDRs (for example `198.51.100.0/24`,
or `0.0.0.0/0` to tunnel all IPv4 traffic). When selecting this node as a peer
--
2.47.3
next reply other threads:[~2026-05-21 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 13:08 Stefan Hanreich [this message]
2026-05-22 7:20 ` applied: [PATCH pve-docs 1/1] sdn: fabrics: wireguard: update endpoint documentation Thomas Lamprecht
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=20260521130857.373765-1-s.hanreich@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pve-devel@lists.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.