From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 167B91FF0AA for ; Tue, 17 Nov 2026 19:45:00 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id F11FB2167A; Tue, 17 Nov 2026 19:44:54 +0100 (CET) Message-ID: <8587ca40-c794-46bb-812d-8b2ef046e6e2@proxmox.com> Date: Tue, 17 Nov 2026 19:44:42 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: superseded: [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} 0/5] Add MTU setting to WireGuard interfaces To: pve-devel@lists.proxmox.com References: <20260626133357.274255-1-s.hanreich@proxmox.com> Content-Language: en-US From: Stefan Hanreich In-Reply-To: <20260626133357.274255-1-s.hanreich@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.228 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: YBJYLLBFHKKKLEB5OFERSH6F6P4G6G5T X-Message-ID-Hash: YBJYLLBFHKKKLEB5OFERSH6F6P4G6G5T X-MailFrom: s.hanreich@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: https://lore.proxmox.com/pve-devel/20261117184346.760458-1-s.hanreich@proxmox.com/T/#t On 6/26/26 3:33 PM, Stefan Hanreich wrote: > This patch series adds support for configuring the MTU for WireGuard interfaces. > Since changing the default value in the API would be breaking, make it a soft > default by pre-filling the MTU value in the UI with 1420, which should work for > most use-cases, as it is the maximum MTU possible if using Ethernet with IPv6. > > > proxmox-ve-rs: > > Stefan Hanreich (1): > wireguard: add mtu option to wireguard interface properties > > .../sdn/fabric/section_config/protocol/wireguard.rs | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > > proxmox-perl-rs: > > Stefan Hanreich (1): > fabrics: wireguard: render mtu to interface config > > pve-rs/src/bindings/sdn/fabrics.rs | 5 +++++ > 1 file changed, 5 insertions(+) > > > pve-network: > > Stefan Hanreich (1): > fabrics: wireguard: add mtu to interface properties > > src/PVE/Network/SDN/Fabrics.pm | 7 +++++++ > 1 file changed, 7 insertions(+) > > > pve-manager: > > Stefan Hanreich (1): > fabrics: wireguard: add mtu to interface properties > > www/manager6/sdn/fabrics/wireguard/InterfacePanel.js | 9 +++++++++ > 1 file changed, 9 insertions(+) > > > pve-docs: > > Stefan Hanreich (1): > sdn: fabrics: wireguard: document mtu option > > pvesdn.adoc | 2 ++ > 1 file changed, 2 insertions(+) > > > Summary over all repositories: > 5 files changed, 36 insertions(+), 0 deletions(-) >