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 93ED61FF09C for ; Mon, 02 Nov 2026 15:57:46 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 8F83F21800; Mon, 02 Nov 2026 15:57:03 +0100 (CET) From: Hannes Laimer To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs v2 11/11] sdn: ipam: document the per-zone VRF and section in NetBox and phpIPAM Date: Mon, 2 Nov 2026 15:56:30 +0100 Message-ID: <20261102145630.1555953-12-h.laimer@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261102145630.1555953-1-h.laimer@proxmox.com> References: <20261102145630.1555953-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: 1793631405961 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.359 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: PXZKC7Z5E5DFNEIK7VZXTRKC2E72RR42 X-Message-ID-Hash: PXZKC7Z5E5DFNEIK7VZXTRKC2E72RR42 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: Every zone's subnets now go into a VRF or a sub-section named after the zone, which is what an admin sees in the IPAM, and a prefix or subnet from before stays where it is. Signed-off-by: Hannes Laimer --- pvesdn.adoc | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/pvesdn.adoc b/pvesdn.adoc index 3fd3533ad07f..75ac781e8c92 100644 --- a/pvesdn.adoc +++ b/pvesdn.adoc @@ -1287,6 +1287,18 @@ Fingerprint:: The SHA-256 fingerprint of the NetBox API. Can be retrieved with `openssl x509 -in /etc/ssl/certs/netbox.crt -noout -fingerprint -sha256` when using the default certificate. +{pve} creates a VRF named `pve-` for every zone, together with the first +subnet of the zone, and keeps the prefixes of the zone's subnets in it. This way +two zones can use the same subnet. The IP addresses allocated in a prefix carry +the MAC address of the guest in their description. Prefixes that earlier +versions created in the global table are still found there and can be moved +into the VRF of their zone, together with their IP addresses and IP ranges. A +zone from before gets its VRF only with the next subnet added to it, so to move +prefixes into it earlier, create the VRF `pve-` by hand. Creating a +subnet whose range the global table still holds is refused, since a prefix in +the VRF would hide the addresses recorded in the old one, so move or remove +that prefix first. + [[pvesdn_ipam_plugin_phpipam]] phpIPAM Plugin @@ -1304,6 +1316,19 @@ Token:: An API access token Section:: An integer ID. Sections are a group of subnets in phpIPAM. Default installations use `sectionid=1` for customers. +{pve} creates a sub-section named `pve-` under the configured section for +every zone, together with the first subnet of the zone, and keeps the zone's +subnets in it. This way two zones can use the same subnet. phpIPAM nests +sections one level deep, so a configured section that is itself a sub-section +gets no sub-sections and the subnets of all zones stay in it. Subnets that +earlier versions created in the configured section itself are still found there +and can be moved into the sub-section of their zone. A zone from before gets its +sub-section only with the next subnet added to it, so to move subnets into it +earlier, create the sub-section `pve-` under the configured section by +hand. Creating a subnet whose range the configured section still holds is +refused, since a copy in the sub-section would hide the addresses recorded in +the old one, so move or remove that subnet first. + [[pvesdn_config_dns]] DNS -- 2.47.3