From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs] pveproxy: document LISTEN_IP setting
Date: Sat, 24 Apr 2021 19:41:43 +0200 [thread overview]
Message-ID: <53b8e375-5b95-9bb7-82fa-1e70cc082e5a@proxmox.com> (raw)
In-Reply-To: <20210423155814.26847-1-s.ivanov@proxmox.com>
On 23.04.21 17:58, Stoiko Ivanov wrote:
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> pveproxy.adoc | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
applied, thanks! Fixed a typo and noted that both pveproxy and spiceproxy are
affected by this change.
> diff --git a/pveproxy.adoc b/pveproxy.adoc
> index d50d04a..0ea5658 100644
> --- a/pveproxy.adoc
> +++ b/pveproxy.adoc
> @@ -59,6 +59,24 @@ The default policy is `allow`.
> |===========================================================
>
>
> +Listening IP
> +------------
> +
> +By setting `LISTEN_IP` in `/etc/default/pveproxy` you can control to which IP
> +address the daemon binds. The IP address needs to be configured on the system.
> +
> +This can be used to listen only to an internal interface and thus have less
> +exposure to the public internet:
> +
> + LISTEN_IP="192.0.2.1"
> +
> +Similarly you can also set a n IPv6 address:
> +
> + LISTEN_IP="2001:db8:85a3::1"
> +
> +WARNING: The nodes in a cluster need access to pveproxy for communictation.
s/communictation/communication/
> +It is not recommended to set `LISTEN_IP` on clustered systems.
> +
> SSL Cipher Suite
> ----------------
>
>
prev parent reply other threads:[~2021-04-24 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 15:58 [pve-devel] " Stoiko Ivanov
2021-04-24 17:41 ` 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=53b8e375-5b95-9bb7-82fa-1e70cc082e5a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.