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 3E6711FF183 for ; Wed, 27 Aug 2025 16:46:52 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5AA611D490; Wed, 27 Aug 2025 16:46:47 +0200 (CEST) Date: Wed, 27 Aug 2025 10:32:53 -0400 To: pve-user@lists.proxmox.com References: <912e37adbc53f89115d2f3543aa1d11366ff8eef.camel@groupe-cyllene.com> In-Reply-To: <912e37adbc53f89115d2f3543aa1d11366ff8eef.camel@groupe-cyllene.com> MIME-Version: 1.0 Message-ID: List-Id: Proxmox VE user list List-Post: From: Miguel Tudela via pve-user Precedence: list Cc: Miguel Tudela X-Mailman-Version: 2.1.29 X-BeenThere: pve-user@lists.proxmox.com List-Subscribe: , List-Unsubscribe: , List-Archive: Reply-To: Proxmox VE user list List-Help: Subject: Re: [PVE-User] address flexibility Content-Type: multipart/mixed; boundary="===============1163648479391160700==" Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" This is a multi-part message in MIME format. --===============1163648479391160700== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: X-Original-To: pve-user@lists.proxmox.com Delivered-To: pve-user@lists.proxmox.com 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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id BDA19D6856 for ; Wed, 27 Aug 2025 16:46:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5A6FC1D365 for ; Wed, 27 Aug 2025 16:46:45 +0200 (CEST) Received: from netlinux.cl (dozer.netlinux.cl [200.75.30.188]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 27 Aug 2025 16:46:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gruposolux.com; s=default; h=In-Reply-To:From:References:To:Subject: MIME-Version:Date:Message-ID:Content-Type:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=jPEDFP1abbSMgPFfS8BJMBuq61ZnFOQuiK4ZF+8Me14=; b=AX6Cqefl/QMuccYxEjYfhGWmYk 2MndLFZgtFm9C8LvRn8y7Tvzxdq5tA3H0cpPktwBVmDyB+BK4FGuhfKcF/22VG93ieKQNZ9ZVSxWB UV2U2Vcs7N4tYeMCfqDOQUP6hUK5DpRsKtlWWETkpfCn8QMvxt/RWKJy8k/QFlMAy5vU=; Received: from maskedhost [127.0.0.1] by netlinux.cl stage1 with esmtpsa (Exim MailCleaner) id 1urHCn-000000008IZ-3WWo for from ; Wed, 27 Aug 2025 10:32:53 -0400 X-MailCleaner-SPF: pass Message-ID: Date: Wed, 27 Aug 2025 10:32:53 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PVE-User] address flexibility To: pve-user@lists.proxmox.com References: <912e37adbc53f89115d2f3543aa1d11366ff8eef.camel@groupe-cyllene.com> Content-Language: en-US, es-ES From: Miguel Tudela In-Reply-To: <912e37adbc53f89115d2f3543aa1d11366ff8eef.camel@groupe-cyllene.com> X-MailCleaner-TrustedIPs: Ok X-MailCleaner-TLS-Client-Certificate: none X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy HTML_MESSAGE 0.001 HTML included in message 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_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com,gruposolux.com] Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Don't forget to reboot after updating the /etc/hosts file, so that PVE updates the server certificate, and it has the hostname and IP address updated in this certificate, since this is verified when connecting the node to a cluster. El 27-08-25 a las 10:30, DERUMIER, Alexandre escribió: >>> i build new proxmox nodes in the lab on a lab network.  i do the >>> debian >>> part in the lab and then the proxmox part in the destination rack >>> because i am not confident that proxmox install does not bind to / >>> embed >>> the ip address on which it is installed. >>> >>> am i being too cautious.  can in build a node, then ship to rack, >>> change >>> /etc/hosts, network config, etc., and then join the cluster? > yes, no problem > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user --===============1163648479391160700== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user --===============1163648479391160700==--