From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs v7 20/21] sdn: zones: document the MTU taken from the underlay interface
Date: Thu, 12 Nov 2026 13:42:00 +0100 [thread overview]
Message-ID: <20261112124201.2844423-21-h.laimer@proxmox.com> (raw)
In-Reply-To: <20261112124201.2844423-1-h.laimer@proxmox.com>
Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
---
pvesdn.adoc | 19 +++++++++++++------
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/pvesdn.adoc b/pvesdn.adoc
index 72f597859e5a..c8f0bd70c6e2 100644
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -308,8 +308,11 @@ Peers Address List:: A list of IP addresses of each node in the VXLAN zone. This
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.
+MTU:: Because VXLAN encapsulation uses 50 bytes over IPv4 and 70 bytes over
+ IPv6, the MTU needs to be that much lower than the outgoing physical
+ interface. Optional, defaults to the MTU configured on the interface holding
+ this node's peer address minus the encapsulation. Without such an interface
+ or MTU, it defaults to 1450 over IPv4 and 1430 over IPv6.
[[pvesdn_zone_plugin_evpn]]
@@ -368,9 +371,12 @@ Disable ARP ND Suppression:: Don't suppress ARP or ND (Neighbor Discovery)
Route-target Import:: Allows you to import a list of external EVPN route
targets. Used for cross-DC or different EVPN network interconnects. Optional.
-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.
+MTU:: Because VXLAN encapsulation uses 50 bytes over IPv4 and 70 bytes over
+ IPv6, the MTU needs to be that much less than the maximal MTU of the outgoing
+ physical interface. Optional, defaults to the MTU configured on the
+ interface holding this node's address from the controller's peers minus the
+ encapsulation. Without such an interface or MTU, it defaults to 1450 over
+ IPv4 and 1430 over IPv6.
[[pvesdn_config_vnet]]
@@ -1763,7 +1769,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
next prev parent reply other threads:[~2026-11-12 12:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 12:41 [PATCH container/docs/manager/network/proxmox{,-perl-rs,-ve-rs}/qemu-server v7 00/21] sdn: implement DHCP for all zones using eBPF Hannes Laimer
2026-11-12 12:41 ` [PATCH proxmox v7 01/21] network-types: mac address: add an accessor for the bytes Hannes Laimer
2026-11-12 12:41 ` [PATCH proxmox-perl-rs v7 02/21] pve-rs: sdn: add bindings for the eBPF DHCP responder Hannes Laimer
2026-11-12 12:41 ` [PATCH proxmox-perl-rs v7 03/21] pve-rs: fire the pve-ebpf-update trigger on upgrade Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-network v7 04/21] sdn: zones: take the VXLAN and EVPN MTU from the underlay interface Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-network v7 05/21] sdn: zones: account for IPv6 in the VXLAN and EVPN MTU Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-network v7 06/21] sdn: dhcp: make the lease time configurable per subnet Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-network v7 07/21] sdn: dhcp: require a backend only if a zone on this node uses it Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-network v7 08/21] bpf: add the build, the package and a native harness for BPF programs Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-network v7 09/21] sdn: dhcp: add the per-tap DHCPv4 responder program Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-network v7 10/21] sdn: dhcp: add an eBPF backend answering on each guest interface Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-network v7 11/21] sdn: zones: report interface plugs and unplugs to the DHCP backends Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-network v7 12/21] sdn: zones: factor out the underlay lookup of VXLAN and EVPN zones Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-network v7 13/21] sdn: zones: allow the ebpf DHCP backend on every zone type Hannes Laimer
2026-11-12 12:41 ` [PATCH qemu-server v7 14/21] network: sdn: keep the DHCP backends current on guest NICs Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-container v7 15/21] net: report NIC plugs and removals to the SDN DHCP backends Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-manager v7 16/21] ui: sdn: add zone DHCP backend selector and subnet DHCP options Hannes Laimer
2026-11-12 12:41 ` [PATCH pve-manager v7 17/21] sdn: bring up the DHCP backends at boot before the guests start Hannes Laimer
2026-11-12 12:41 ` [PATCH proxmox-ve-rs v7 18/21] ve-config: sdn: add the ebpf dhcp backend Hannes Laimer
2026-11-12 12:41 ` [PATCH proxmox-ve-rs v7 19/21] sdn-dhcp: add the crate that runs the eBPF DHCP responder Hannes Laimer
2026-11-12 12:42 ` Hannes Laimer [this message]
2026-11-12 12:42 ` [PATCH pve-docs v7 21/21] sdn: dhcp: add eBPF backend section Hannes Laimer
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=20261112124201.2844423-21-h.laimer@proxmox.com \
--to=h.laimer@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.