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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 51D0568DB5 for ; Wed, 10 Feb 2021 18:02:15 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 39CB8BA9A for ; Wed, 10 Feb 2021 18:02:15 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (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 id 29F3CBA8A for ; Wed, 10 Feb 2021 18:02:14 +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 E269846200 for ; Wed, 10 Feb 2021 18:02:13 +0100 (CET) Message-ID: <9d2d0654-5649-2395-0d3a-c913cf8448df@proxmox.com> Date: Wed, 10 Feb 2021 18:02:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:86.0) Gecko/20100101 Thunderbird/86.0 Content-Language: en-US To: Proxmox VE development discussion , Oguz Bektas References: <20210210160142.1326921-1-o.bektas@proxmox.com> From: Thomas Lamprecht In-Reply-To: <20210210160142.1326921-1-o.bektas@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.071 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.265 Looks like a legit reply (A) 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [utils.pm, pveproxy.pm] Subject: Re: [pve-devel] [RFC http-server manager 0/2] fix #2997: allow setting BIND_IP for proxy 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, 10 Feb 2021 17:02:15 -0000 On 10.02.21 17:01, Oguz Bektas wrote: > maybe a simple approach like this is okay? > I'd rather go the way PBS does, just listen on really all by default. PVE often uses multiple networks where the proxy needs to be able on more than one, a single settign may not cut it in all setups. It's simpler to just always listen on all and let admins restrict with FW where required. > can also be called "LISTEN_IP" or similar > > pve-manager: > > Oguz Bektas (1): > proxy: allow setting BIND_IP for pveproxy > > PVE/Service/pveproxy.pm | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > > pve-http-server: > > Oguz Bektas (1): > utils: add BIND_IP option in /etc/default/pveproxy > > PVE/APIServer/Utils.pm | 3 +++ > 1 file changed, 3 insertions(+) >