Hi, I'm starting to use gluster version debian/unstable 3.4.0-4 but I need use ipv6 in my network, but just can't setup glusterfs for. I tried configuring IPv6 or DNS (only resolving at IPv6), got errors in both case. Here last test I did + error: /usr/sbin/glusterfsd -s ipv6.google.com --volfile-id testvol5.XXX.... [2013-09-30 14:09:24.424624] E [common-utils.c:211:gf_resolve_ip6] 0-resolver: getaddrinfo failed (System error) [2013-09-30 14:09:24.424683] E [name.c:249:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host ipv6.google.com On same computer: #host ipv6.google.com ipv6.google.com is an alias for ipv6.l.google.com. ipv6.l.google.com has IPv6 address 2404:6800:4008:c01::63 jclift on irc told me that some works were in progress about ipv6, and to ask on mailing list. Any patch to apply? Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: kreatin.vcard Type: text/x-vcard Size: 183 bytes Desc: not available URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130930/d85f5743/attachment.vcf> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130930/d85f5743/attachment.sig>
Am 30.09.2013 16:24, schrieb Micka?l Villers:> Hi,Hi,> > I'm starting to use gluster version debian/unstable 3.4.0-4 > but I need use ipv6 in my network, but just can't setup glusterfs for. > > I tried configuring IPv6 or DNS (only resolving at IPv6), got errors in both case.I also need IPv6 support (AFAIK it's not possible to use a server whose IPv4 address might change which would require repeated DNS lookups[*])--however, as a quick workaround, using stunnel comes to mind, which lets you specify a local IPv4 address and in turn will connect to the real IPv6 address through a tunnel. Alternatively, ssh/netcat might both be worth a look (the latter should allow to turn off encryption if two-factor authentication is not needed and you want to get rid of the "encryption overhead"). [*] that scenario can be addressed by re-establishing the aforementioned tunnel whenever the IP address changes Kind regards, Markus