<div dir="ltr">The IPV6 implementation in Gluster requires that IPV6 be enabled in the kernel and that getaddrinfo works for AF_INET6. This is why IPV6_DEFAULT is disabled by default, and is only enabled if GlusterFS is configured with `--with-ipv6-default`.<div>This has been the case since it was introduced in 3.13.</div><div><br></div><div>The change v5.0 debian packages that is causing the failures seems to be that glusterfs is configured with `--with-ipv6-default` enabled. This needs to be disabled for now. The packages provided by other distributions do not enable this.</div><div><br></div><div>The IPV6 changes were contributed to GlusterFS by Facebook, and are designed to run on their internal networks which are all IPV6 enabled. The `--with-ipv6-default` flag is provided for their convenience, and is disabled by default. There hasn't been any further contributions to this to make it suitable for everyone as there hasn't been a lot of community ask for it.</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 22, 2018 at 2:19 PM Patrick Matthäi <<a href="mailto:pmatthaei@debian.org" target="_blank">pmatthaei@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hi,</p>
<p>looks like my MUA didn't send the message..</p>
<p>Our users have problems with the --with-ipv6-default option, they
are not able to connect at all. Could you help here?<br>
</p>
<div class="m_-5802774704358822534m_7715885059853395072moz-forward-container"><br>
-------- Weitergeleitete Nachricht --------
<table class="m_-5802774704358822534m_7715885059853395072moz-email-headers-table" cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<th nowrap valign="BASELINE" align="RIGHT">Betreff:
</th>
<td>Bug#914125: Peering on glusterfs-server (version >5)
impossible under IPv4 on Buster</td>
</tr>
<tr>
<th nowrap valign="BASELINE" align="RIGHT">Weitersenden-Datum:
</th>
<td>Mon, 19 Nov 2018 17:15:02 +0000</td>
</tr>
<tr>
<th nowrap valign="BASELINE" align="RIGHT">Weitersenden-Von:
</th>
<td>Emmanuel Quemener <a class="m_-5802774704358822534m_7715885059853395072moz-txt-link-rfc2396E" href="mailto:emmanuel.quemener@gmail.com" target="_blank"><emmanuel.quemener@gmail.com></a></td>
</tr>
<tr>
<th nowrap valign="BASELINE" align="RIGHT">Weitersenden-An:
</th>
<td><a class="m_-5802774704358822534m_7715885059853395072moz-txt-link-abbreviated" href="mailto:debian-bugs-dist@lists.debian.org" target="_blank">debian-bugs-dist@lists.debian.org</a></td>
</tr>
<tr>
<th nowrap valign="BASELINE" align="RIGHT">Weitersenden-CC:
</th>
<td>Patrick Matthäi <a class="m_-5802774704358822534m_7715885059853395072moz-txt-link-rfc2396E" href="mailto:pmatthaei@debian.org" target="_blank"><pmatthaei@debian.org></a></td>
</tr>
<tr>
<th nowrap valign="BASELINE" align="RIGHT">Datum: </th>
<td>Mon, 19 Nov 2018 18:12:46 +0100</td>
</tr>
<tr>
<th nowrap valign="BASELINE" align="RIGHT">Von: </th>
<td>Emmanuel Quemener <a class="m_-5802774704358822534m_7715885059853395072moz-txt-link-rfc2396E" href="mailto:emmanuel.quemener@gmail.com" target="_blank"><emmanuel.quemener@gmail.com></a></td>
</tr>
<tr>
<th nowrap valign="BASELINE" align="RIGHT">Antwort
an: </th>
<td>Emmanuel Quemener <a class="m_-5802774704358822534m_7715885059853395072moz-txt-link-rfc2396E" href="mailto:emmanuel.quemener@gmail.com" target="_blank"><emmanuel.quemener@gmail.com></a>,
<a class="m_-5802774704358822534m_7715885059853395072moz-txt-link-abbreviated" href="mailto:914125@bugs.debian.org" target="_blank">914125@bugs.debian.org</a></td>
</tr>
<tr>
<th nowrap valign="BASELINE" align="RIGHT">An: </th>
<td><a class="m_-5802774704358822534m_7715885059853395072moz-txt-link-abbreviated" href="mailto:submit@bugs.debian.org" target="_blank">submit@bugs.debian.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Package: glusterfs-server
Version: 5.1-1
1) When I install the glusterfs-server with a version >5, peering is
impossible in IPv4 on buster distribution.
# apt install glusterfs-server
# systemctl start glusterd
# systemctl start glustereventsd
# gluster peer probe 140.77.79.200
peer probe: success. Probe on localhost not needed
# gluster peer probe 140.77.79.185
peer probe: failed: Probe returned with Transport endpoint is not connected
When I look inside the logs in /var/log/glusterfs/glusterd.log
[2018-11-19 16:50:37.051633] E [MSGID: 101075] [common-
utils.c:508:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Address
family for hostname not supported)
[2018-11-19 16:50:37.051638] E
[name.c:258:af_inet_client_get_remote_sockaddr] 0-management: DNS
resolution failed on host 140.77.79.185
2) It's working on glusterfs-server version 4 but without firewalld
package.
3) It's working with glusterfs-server version 5.1 when I REMOVE the 2
following options inside debian/rules AND without firewalld :
DEB_CONFIGURE_EXTRA_FLAGS := \
--enable-firewalld \
--with-ipv6-default
I also try without any success to use the following options to fall back
on IPv4 options in /etc/glusterfs/glusterd.vol :
option transport-type socket/inet,rdma
option transport.address-family inet
Best regards.
EQ
</pre>
</div>
</div>
_______________________________________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/maintainers</a><br>
</blockquote></div>