<div dir="ltr">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.<div>
<br></div><div>Thanks for clarifying; that saves me some debugging.</div><div><br></div><div>Sjon Hortensius</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 5, 2014 at 8:07 PM, Justin Clift <span dir="ltr"><<a href="mailto:justin@gluster.org" target="_blank">justin@gluster.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 05/06/2014, at 4:20 PM, Sjon Hortensius wrote:<br>
> 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.<br>
><br>
> I have tried peer probe on a ipv6-only hostname and an ipv6 address; but there doesn't seem to be any progress.<br>
><br>
> 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)"<br>
><br>
> 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"<br>
><br>
> 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.<br>
<br>
</div></div>From memory, IPv6 support is something we're working on for GlusterFS<br>
3.6. It's probably not something we'd really recommend with the current<br>
releases. :(<br>
<br>
+ Justin<br>
<br>
--<br>
Open Source and Standards @ Red Hat<br>
<br>
<a href="http://twitter.com/realjustinclift" target="_blank">twitter.com/realjustinclift</a><br>
<br>
</blockquote></div><br></div>