all lists on 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 5/5] sdn: fabrics: wireguard: document mtu option
Date: Fri, 26 Jun 2026 15:33:55 +0200	[thread overview]
Message-ID: <20260626133357.274255-6-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20260626133357.274255-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 a09a443..b5e500b 100644
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -933,6 +933,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.
 
+Listen Port:: 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-06-26 13:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 13:33 [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} 0/5] Add MTU setting to WireGuard interfaces Stefan Hanreich
2026-06-26 13:33 ` [PATCH proxmox-ve-rs 1/5] wireguard: add mtu option to wireguard interface properties Stefan Hanreich
2026-06-26 13:33 ` [PATCH proxmox-perl-rs 2/5] fabrics: wireguard: render mtu to interface config Stefan Hanreich
2026-06-26 13:33 ` [PATCH pve-network 3/5] fabrics: wireguard: add mtu to interface properties Stefan Hanreich
2026-06-26 13:33 ` [PATCH pve-manager 4/5] " Stefan Hanreich
2026-06-26 13:33 ` 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=20260626133357.274255-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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal