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 20F2E1FF0E3 for ; Tue, 27 Oct 2026 10:02:18 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id D582321B24; Tue, 27 Oct 2026 09:57:10 +0100 (CET) From: Hannes Laimer To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs v3 44/45] sdn: zones: document the VXLAN-GBP option Date: Tue, 27 Oct 2026 09:55:26 +0100 Message-ID: <20261027085527.702738-45-h.laimer@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261027085527.702738-1-h.laimer@proxmox.com> References: <20261027085527.702738-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: 1793091381510 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.358 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: MDQ2L6KE3C7EFMOPSQCYUTOXYNJHYV22 X-Message-ID-Hash: MDQ2L6KE3C7EFMOPSQCYUTOXYNJHYV22 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: EVPN zones run on VXLAN interfaces as well, so the EVPN section gets the same entry as the VXLAN one. Signed-off-by: Hannes Laimer --- pvesdn.adoc | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/pvesdn.adoc b/pvesdn.adoc index 3fd3533ad07f..7a674597d470 100644 --- a/pvesdn.adoc +++ b/pvesdn.adoc @@ -310,6 +310,18 @@ SDN Fabric:: Instead of manually defining all the peers, use a MTU:: Because VXLAN encapsulation uses 50 bytes, the MTU needs to be 50 bytes lower than the outgoing physical interface. +VXLAN-GBP:: Enable VXLAN Group Based Policy (GBP) on the zone's VXLAN + interfaces. GBP carries a 16-bit group ID in the VXLAN header, taken from + the packet mark on the sending node and restored on the receiving one. + Every VTEP in the zone must have it enabled, since one without it drops + GBP-tagged traffic. All zones that use the same VXLAN port must agree on + this option, an SDN apply refuses a configuration where they do not. + Optional. + +NOTE: The kernel sets GBP only when it creates a VXLAN interface. Changing the +option on an existing zone therefore recreates the zone's VXLAN interfaces on +the next apply, which briefly interrupts traffic. + [[pvesdn_zone_plugin_evpn]] EVPN Zones @@ -371,6 +383,18 @@ 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. +VXLAN-GBP:: Enable VXLAN Group Based Policy (GBP) on the zone's VXLAN + interfaces. GBP carries a 16-bit group ID in the VXLAN header, taken from + the packet mark on the sending node and restored on the receiving one. + Every VTEP in the zone must have it enabled, since one without it drops + GBP-tagged traffic. All zones that use the same VXLAN port must agree on + this option, an SDN apply refuses a configuration where they do not. + Optional. + +NOTE: The kernel sets GBP only when it creates a VXLAN interface. Changing the +option on an existing zone therefore recreates the zone's VXLAN interfaces on +the next apply, which briefly interrupts traffic. + [[pvesdn_config_vnet]] VNets -- 2.47.3