From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 5E3CD1FF0AF for ; Fri, 20 Nov 2026 08:43:13 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 4CEB221720; Fri, 20 Nov 2026 08:42:55 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Subject: Re: [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} v2 0/5] Add MTU setting to WireGuard interfaces Date: Fri, 20 Nov 2026 08:42:43 +0100 Message-ID: <179515721880.2281522.4954112049046065274.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261117184346.760458-1-s.hanreich@proxmox.com> References: <20261117184346.760458-1-s.hanreich@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1795160569309 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.024 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) KAM_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish 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: L5W3AQKK7MCIOOH6TQ647GDOM3IZDBN2 X-Message-ID-Hash: L5W3AQKK7MCIOOH6TQ647GDOM3IZDBN2 X-MailFrom: t.lamprecht@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: On Tue, 17 Nov 2026 19:43:39 +0100, 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. > > Changes from v1: > * rebase on top of current master > * fix documentation key > * change API type from number to integer > > [...] Applied, thanks! Tested on a three-node cluster: the MTU is applied, and the UI fills in 1420 for new interfaces. What I changed in your patches: the Rust side now enforces the same MTU limits as the Perl side, and the docs explain the WireGuard overhead and that interfaces without an MTU, including all existing ones, get the ifupdown2 default, usually 1500, and not the 1420 of WireGuard. What I added on top: I raised the minimum MTU from 576 to 1280. Below that, the kernel turns off IPv6 on the interface, which makes ifreload fail if it has an IPv6 address and drops the IPv6 routes to the peers. This rules out IPv4-only tunnels below 1280, which I don't think fabrics need; shout if you see that differently. Still open: the interface panel silently keeps the last valid MTU or listen port if you enter an invalid one, instead of refusing to save. [proxmox-perl-rs] [2/5] fabrics: wireguard: render mtu to interface config commit: 66c8b3b2b894f45c5a710b1b264af653d0bf9f1b [proxmox-ve-rs] [1/5] wireguard: add mtu option to wireguard interface properties commit: f8f76c236768094475f7cd2434d431f0c86ed12b [pve-docs] [5/5] sdn: fabrics: wireguard: document mtu option commit: 1f39d9d56c73b2f791114a4441140cb1000653b3 [pve-manager] [4/5] fabrics: wireguard: add mtu to interface properties commit: b739cd12383ad5be4822c0af2b600a8c9890c8f3 [pve-network] [3/5] fabrics: wireguard: add mtu to interface properties commit: 018781b60dd78c0bec0a639b6b9937fc7171573c