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 02C2E1FF0DF for ; Thu, 05 Nov 2026 11:06:44 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 291C021730; Thu, 05 Nov 2026 11:05:48 +0100 (CET) From: Hannes Laimer To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs v6 16/17] sdn: zones: document the MTU taken from the underlay interface Date: Thu, 5 Nov 2026 11:03:15 +0100 Message-ID: <20261105100316.449163-17-h.laimer@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261105100316.449163-1-h.laimer@proxmox.com> References: <20261105100316.449163-1-h.laimer@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793873085050 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.285 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: 2H6WZUW56K5AKZG32DI4ELJCA2RQ7KM2 X-Message-ID-Hash: 2H6WZUW56K5AKZG32DI4ELJCA2RQ7KM2 X-MailFrom: h.laimer@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: Signed-off-by: Hannes Laimer --- pvesdn.adoc | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/pvesdn.adoc b/pvesdn.adoc index 407986901ff2..24d4f967cf4d 100644 --- a/pvesdn.adoc +++ b/pvesdn.adoc @@ -308,7 +308,9 @@ SDN Fabric:: Instead of manually defining all the peers, use a xref:pvesdn_config_fabrics[Fabric] for automatically generating the peer list. MTU:: Because VXLAN encapsulation uses 50 bytes, the MTU needs to be 50 bytes - lower than the outgoing physical interface. + lower than the outgoing physical interface. Optional, defaults to the MTU + configured on the interface holding this node's peer address minus 50 bytes. + Without such an interface or MTU, it defaults to 1450. [[pvesdn_zone_plugin_evpn]] @@ -369,7 +371,9 @@ Route-target Import:: Allows you to import a list of external EVPN route MTU:: Because VXLAN encapsulation uses 50 bytes, the MTU needs to be 50 bytes less than the maximal MTU of the outgoing physical interface. Optional, - defaults to 1450. + defaults to the MTU configured on the interface holding this node's address + from the controller's peers minus 50 bytes. Without such an interface or MTU, + it defaults to 1450. [[pvesdn_config_vnet]] @@ -1762,7 +1766,8 @@ The example assumes a cluster with three nodes, with the node IP addresses 192.168.0.1, 192.168.0.2 and 192.168.0.3. Create a VXLAN zone named `myvxlanzone` and add all IPs from the nodes to the -peer address list. Use the default MTU of 1450 or configure accordingly. +peer address list. Leave the MTU unset or configure accordingly. Without an MTU +configured on the interfaces holding these addresses, the zone uses 1450. ---- ID: myvxlanzone -- 2.47.3