[Gluster-users] Gluster-3.5.0 Refusing to connect over ipv6
adam.huffman at gmail.com
Thu Jun 12 12:18:29 UTC 2014
Is there a way of preventing Gluster from trying IPv6 first? I would
rather not have to disable it on the host entirely, because we're
increasingly using it more generally.
On Fri, Jun 6, 2014 at 9:06 AM, Niels de Vos <ndevos at redhat.com> wrote:
> On Fri, Jun 06, 2014 at 09:26:12AM +0200, Sjon Hortensius wrote:
>> That is a very definite and clear statement, thanks! When searching for
>> gluster + ipv6; I found multiple people saying they have this working; or
>> it should just work (from as far back as 2011). I assumed the same code
>> should be in 3.5 and still be functional; but my assumption was incorrect.
> There are some bugs filed that sound like the problem you are seeing:
> Bug 910836 - peer probe over ipv6 on ipv4/ipv6 network fails.
> Bug 922801 - Gluster not resolving hosts with IPv6 only lookups
> Bug 1070685 - glusterfs ipv6 functionality not working
> If you have additional information on issue, it'll be appreciated if you
> can add that. In case you have also noticed a different problem, please
> create a new bug for it.
> Some issues look relatively easy to solve. If that is indeed the case,
> don't hesitate to send patches. Of course, you're also welcome to send
> patches for complex bugs ;-)
>> Thanks for clarifying; that saves me some debugging.
>> Sjon Hortensius
>> On Thu, Jun 5, 2014 at 8:07 PM, Justin Clift <justin at gluster.org> wrote:
>> > On 05/06/2014, at 4:20 PM, Sjon Hortensius wrote:
>> > > After a bit of a struggle to get glusterfsd to listen to ipv6; I am now
>> > having problems trying to get the servers to 'peer probe' each other.
>> > >
>> > > I have tried peer probe on a ipv6-only hostname and an ipv6 address; but
>> > there doesn't seem to be any progress.
>> > >
>> > > common-utils.c:248:gf_resolve_ip6 always returns ipv4 addresses for
>> > hostnames while passing an ipv6 address results in "getaddrinfo failed
>> > (Address family for hostname not supported)"
>> > >
>> > > I suspect this is caused by rpc_transport_inet_options_build which does
>> > "dict_set_str (dict, "transport.address-family", "inet");"; which I think
>> > should be "inet/inet6"
>> > >
>> > > Can anybody confirm or deny this? Might there be a way to override this
>> > from the configuration? If any further information is useful I'll be happy
>> > to supply it.
>> > From memory, IPv6 support is something we're working on for GlusterFS
>> > 3.6. It's probably not something we'd really recommend with the current
>> > releases. :(
>> > + Justin
>> > --
>> > Open Source and Standards @ Red Hat
>> > twitter.com/realjustinclift
>> Gluster-users mailing list
>> Gluster-users at gluster.org
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users