From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 3C93C1FF15D for ; Thu, 3 Oct 2024 10:39:46 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 03A1F1C1D2; Thu, 3 Oct 2024 10:40:05 +0200 (CEST) From: Daniel Herzig To: pve-devel@lists.proxmox.com Date: Thu, 3 Oct 2024 10:38:11 +0200 Message-Id: <20241003083811.39215-1-d.herzig@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH docs] increase verbosity of sdn dhcp docs. X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" These minor additions to and rearrangements within the documentation target easier accessibility for the SDN DHCP feature. Signed-off-by: Daniel Herzig --- pvesdn.adoc | 37 +++++++++++++++++++++++++++++-------- 1 file changed, 29 insertions(+), 8 deletions(-) diff --git a/pvesdn.adoc b/pvesdn.adoc index 39de80f..d4f63fc 100644 --- a/pvesdn.adoc +++ b/pvesdn.adoc @@ -110,6 +110,12 @@ apt install dnsmasq systemctl disable --now dnsmasq ---- +This disables the default dnsmasq service and allows for a separate dnsmasq service for +each configured Zone (`dnsmasq@$ZONE.service`). + +See the corresponding section in xref:pvesdn_config_dhcp[DHCP feature] for +configuration details. + [[pvesdn_install_frrouting]] FRRouting ~~~~~~~~~ @@ -627,14 +633,17 @@ available when using the xref:pvesdn_ipam_plugin_pveipam[PVE IPAM plugin]. Configuration ~~~~~~~~~~~~~ -You can enable automatic DHCP for a zone in the Web UI via the Zones panel and -enabling DHCP in the advanced options of a zone. +NOTE: Currently only Simple Zones have support for automatic DHCP. +Do not forget to follow the installation steps for the +xref:pvesdn_install_dhcp_ipam[dnsmasq DHCP plugin]! -NOTE: Currently only Simple Zones have support for automatic DHCP +You can enable automatic DHCP for a zone in the Web UI via the Zones panel and +enabling DHCP in the advanced options of a Zone. After automatic DHCP has been enabled for a Zone, DHCP Ranges need to be -configured for the subnets in a Zone. In order to that, go to the Vnets panel and -select the Subnet for which you want to configure DHCP ranges. In the edit +configured for the Subnets in a Zone. In order to that, go to the VNets panel and +create a VNet, which is attached to your Zone. Click your VNet and create +the Subnet for which you want to configure DHCP ranges. In the edit dialogue you can configure DHCP ranges in the respective Tab. Alternatively you can set DHCP ranges for a Subnet via the following CLI command: @@ -644,14 +653,26 @@ pvesh set /cluster/sdn/vnets//subnets/ -dhcp-range start-address=10.0.2.100,end-address=10.0.2.200 ---- -You also need to have a gateway configured for the subnet - otherwise +You also need to have a gateway configured for the Subnet - otherwise automatic DHCP will not work. +Make sure the gateway's IP address is within the range of your Subnet +(eg 192.0.2.1 for a Subnet 192.0.2.0/24). This will be the address under +which you can reach your PVE host from the guest. If you want your guests +to have internet access, check the SNAT box as well. + +NOTE: The node will configure the gateway IP with the configured netmask +on the virtual bridge. Keep in mind that this range should not be in use +elsewhere in your network to avoid unexpected routing issues. + +After finishing your configuration, apply it from the SDN panel. + +The configuration results in a Linux bridge (named like your VNet) being configured +with the gateway's IP as its address. + The DHCP plugin will then allocate IPs in the IPAM only in the configured ranges. -Do not forget to follow the installation steps for the -xref:pvesdn_install_dhcp_ipam[dnsmasq DHCP plugin] as well. Plugins ~~~~~~~ -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel