From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 676A9B3E8C for ; Wed, 29 Nov 2023 16:10:36 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4B418A1F1 for ; Wed, 29 Nov 2023 16:10:36 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 29 Nov 2023 16:10:34 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 55AD240EB9 for ; Wed, 29 Nov 2023 16:10:34 +0100 (CET) From: Stoiko Ivanov To: pve-devel@lists.proxmox.com Date: Wed, 29 Nov 2023 16:10:21 +0100 Message-Id: <20231129151021.280645-1-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.089 Adjusted score from AWL reputation of From: address 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH docs] fix #5089: sdn: fix s/quest/guest/ typo 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: , X-List-Received-Date: Wed, 29 Nov 2023 15:10:36 -0000 additionally did a `git grep '\bquest'` for good measure Signed-off-by: Stoiko Ivanov --- pvesdn.adoc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/pvesdn.adoc b/pvesdn.adoc index fdc6ea7..53293b1 100644 --- a/pvesdn.adoc +++ b/pvesdn.adoc @@ -381,7 +381,7 @@ Zone:: The associated zone for this VNet Tag:: The unique VLAN or VXLAN ID VLAN Aware:: Enables vlan-aware option on the interface, enabling configuration - in the quest. + in the guest. [[pvesdn_config_subnet]] @@ -715,17 +715,17 @@ details to enhance comprehension of the available configuration options. Simple Zone Example ~~~~~~~~~~~~~~~~~~~ -Simple zone networks create an isolated network for quests on a single host to +Simple zone networks create an isolated network for guests on a single host to connect to each other. -TIP: connection between quests are possible if all quests reside on a same host +TIP: connection between guests are possible if all guests reside on a same host but cannot be reached on other nodes. * Create a simple zone named `simple`. * Add a VNet names `vnet1`. * Create a Subnet with a gateway and the SNAT option enabled. * This creates a network bridge `vnet1` on the node. Assign this bridge to the - quests that shall join the network and configure an IP address. + guests that shall join the network and configure an IP address. The network interface configuration in two VMs may look like this which allows them to communicate via the 10.0.1.0/24 network. @@ -747,7 +747,7 @@ iface ens19 inet static Source NAT Example ~~~~~~~~~~~~~~~~~~ -If you want to allow outgoing connections for quests in the simple network zone +If you want to allow outgoing connections for guests in the simple network zone the simple zone offers a Source NAT (SNAT) option. Starting from the configuration xref:pvesdn_setup_example_simple[above], Add a @@ -759,10 +759,10 @@ Gateway: 172.16.0.1 SNAT: checked ---- -In the quests configure the static IP address inside the subnet's IP range. +In the guests configure the static IP address inside the subnet's IP range. The node itself will join this network with the Gateway IP '172.16.0.1' and -function as the NAT gateway for quests within the subnet range. +function as the NAT gateway for guests within the subnet range. [[pvesdn_setup_example_vlan]] -- 2.39.2