Re: [libvirt] [PATCH v1] Loop through all resolved addresses in virNetSocketNewListenTCP

2018-05-17 Thread John Ferlan
On 05/17/2018 02:14 AM, Olaf Hering wrote: > Am Wed, 16 May 2018 18:44:32 -0400 > schrieb John Ferlan : > >> On 05/15/2018 04:20 AM, Olaf Hering wrote: >>> Currently virNetSocketNewListenTCP bails out early under the following >>> conditions: >>> - the hostname resolves to at least one IPv4 and

Re: [libvirt] [PATCH v1] Loop through all resolved addresses in virNetSocketNewListenTCP

2018-05-16 Thread Olaf Hering
Am Wed, 16 May 2018 18:44:32 -0400 schrieb John Ferlan : > On 05/15/2018 04:20 AM, Olaf Hering wrote: > > Currently virNetSocketNewListenTCP bails out early under the following > > conditions: > > - the hostname resolves to at least one IPv4 and at least one IPv6 > > address > which produces w

Re: [libvirt] [PATCH v1] Loop through all resolved addresses in virNetSocketNewListenTCP

2018-05-16 Thread John Ferlan
$SUBJ: util: Fix addres On 05/15/2018 04:20 AM, Olaf Hering wrote: > Currently virNetSocketNewListenTCP bails out early under the following > conditions: > - the hostname resolves to at least one IPv4 and at least one IPv6 > address which produces what error? > - the local interfaces have tha

[libvirt] [PATCH v1] Loop through all resolved addresses in virNetSocketNewListenTCP

2018-05-15 Thread Olaf Hering
Currently virNetSocketNewListenTCP bails out early under the following conditions: - the hostname resolves to at least one IPv4 and at least one IPv6 address - the local interfaces have that one IPv4 address assigned, but not any of the IPv6 addresses - the local interfaces have just IPv6 link-