From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Oguz Bektas <o.bektas@proxmox.com>
Subject: Re: [pve-devel] [RFC http-server manager 0/2] fix #2997: allow setting BIND_IP for proxy
Date: Wed, 10 Feb 2021 18:02:13 +0100 [thread overview]
Message-ID: <9d2d0654-5649-2395-0d3a-c913cf8448df@proxmox.com> (raw)
In-Reply-To: <20210210160142.1326921-1-o.bektas@proxmox.com>
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(+)
>
prev parent reply other threads:[~2021-02-10 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 16:01 Oguz Bektas
2021-02-10 16:01 ` [pve-devel] [RFC 1/2 http-server] utils: add BIND_IP option in /etc/default/pveproxy Oguz Bektas
2021-02-10 16:01 ` [pve-devel] [RFC 2/2 manager] proxy: allow setting BIND_IP for pveproxy Oguz Bektas
2021-02-10 16:20 ` Stoiko Ivanov
2021-02-15 10:00 ` Oguz Bektas
2021-02-10 17:02 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d2d0654-5649-2395-0d3a-c913cf8448df@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=o.bektas@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox