From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, o.bektas@proxmox.com
Subject: Re: [pve-devel] [PATCH v3 common 1/3] daemon: listen also on ipv6
Date: Wed, 24 Mar 2021 09:37:03 +0100 [thread overview]
Message-ID: <75ad2e3f-48c4-0ab5-c1ed-95fa268a7025@proxmox.com> (raw)
In-Reply-To: <20210322140045.763332-2-o.bektas@proxmox.com>
Note that for pmgproxy this is still called this with (8006, undef,
$family). Did you ensure that this is backwards-compatible? Otherwise
this needs versioned breaks and the call for pmgproxy needs to be
adapted too.
Am 22.03.21 um 15:00 schrieb Oguz Bektas:
> see [0]
> when we set 'Domain' to PF_INET6 by default, it will prefer IPv6. since
> we don't set 'V6Only' it will also listen on IPv4 interfaces.
>
> 'Family' parameter isn't needed anymore.
>
> this change depends on the changes in pve-manager and pve-http-server to
> work correctly.
>
> [0]:
> https://perldoc.perl.org/IO::Socket::IP#REPLACING-IO::Socket-DEFAULT-BEHAVIOUR
>
> Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
> ---
> src/PVE/Daemon.pm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/PVE/Daemon.pm b/src/PVE/Daemon.pm
> index 64f8126..76601d5 100644
> --- a/src/PVE/Daemon.pm
> +++ b/src/PVE/Daemon.pm
> @@ -820,10 +820,10 @@ sub create_reusable_socket {
> } else {
>
> $socket = IO::Socket::IP->new(
> - LocalAddr => $host,
> + Domain => PF_INET6,
> + LocalHost => $host,
> LocalPort => $port,
> Listen => SOMAXCONN,
> - Family => $family,
> Proto => 'tcp',
> GetAddrInfoFlags => 0,
> ReuseAddr => 1) ||
>
next prev parent reply other threads:[~2021-03-24 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 14:00 [pve-devel] [PATCH v3 http-server common manager 0/3] fix #2997: pveproxy LISTEN address Oguz Bektas
2021-03-22 14:00 ` [pve-devel] [PATCH v3 common 1/3] daemon: listen also on ipv6 Oguz Bektas
2021-03-24 8:37 ` Fabian Ebner [this message]
2021-03-24 10:38 ` Oguz Bektas
2021-03-24 11:00 ` Fabian Ebner
2021-03-24 12:59 ` [pve-devel] [PATCH pmg-api] pmgproxy: allow setting LISTEN_IP parameter Oguz Bektas
2021-03-24 13:20 ` [pve-devel] [PATCH v4 common 1/3] daemon: listen also on ipv6 Oguz Bektas
2021-04-21 16:16 ` [pve-devel] applied: " Thomas Lamprecht
2021-03-22 14:00 ` [pve-devel] [PATCH v3 manager 2/3] proxy: allow setting LISTEN_IP for pveproxy and spiceproxy Oguz Bektas
2021-03-24 8:37 ` Fabian Ebner
2021-03-24 10:03 ` Oguz Bektas
2021-03-22 14:00 ` [pve-devel] [PATCH v3 http-server 3/3] utils: add LISTEN_IP option in /etc/default/pveproxy Oguz Bektas
2021-03-23 13:30 ` Dylan Whyte
2021-04-21 15:44 ` [pve-devel] applied: " Thomas Lamprecht
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=75ad2e3f-48c4-0ab5-c1ed-95fa268a7025@proxmox.com \
--to=f.ebner@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