public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs v2 5/5] sdn: fabrics: wireguard: document mtu option
Date: Tue, 17 Nov 2026 19:43:44 +0100	[thread overview]
Message-ID: <20261117184346.760458-6-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20261117184346.760458-1-s.hanreich@proxmox.com>

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 pvesdn.adoc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/pvesdn.adoc b/pvesdn.adoc
index b701636..c19485b 100644
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -934,6 +934,8 @@ Peers:: A list of peers that should be configured for that interface. All nodes
 that are part of the fabric can be selected as peers - the peer definition will
 be auto-generated from the configuration in the node.
 
+MTU:: The MTU that should be configured for this interface.
+
 When defining an interface, Proxmox VE automatically generates a private key
 for it in `/etc/pve/priv/wg-keys.cfg` upon saving the interface, and stores the
 matching public key alongside the interface in the fabric configuration so it
-- 
2.47.3





      parent reply	other threads:[~2026-11-17 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 18:43 [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} v2 0/5] Add MTU setting to WireGuard interfaces Stefan Hanreich
2026-11-17 18:43 ` [PATCH proxmox-ve-rs v2 1/5] wireguard: add mtu option to wireguard interface properties Stefan Hanreich
2026-11-17 18:43 ` [PATCH proxmox-perl-rs v2 2/5] fabrics: wireguard: render mtu to interface config Stefan Hanreich
2026-11-17 18:43 ` [PATCH pve-network v2 3/5] fabrics: wireguard: add mtu to interface properties Stefan Hanreich
2026-11-17 18:43 ` [PATCH pve-manager v2 4/5] " Stefan Hanreich
2026-11-17 18:43 ` Stefan Hanreich [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=20261117184346.760458-6-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal