<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en">
<head>
<meta content="text/html; charset=US-ASCII" http-equiv="Content-Type">
<title>
GitLab
</title>
<style>img {
max-width: 100%; height: auto;
}
</style>
</head>
<body>
<div class="content">
<p style="color: #777777;">
<a href="https://gitlab.com/ametzler">Andreas Metzler</a>
commented:
</p>
<div style="">
<p dir="auto">Julien Cristau and Adrian Bunk have shed some light on this in <a href="https://bugs.debian.org/962218" rel="nofollow noreferrer noopener" target="_blank">https://bugs.debian.org/962218</a></p>
<p dir="auto">The respective buildd has IPv6 connectivity, the IPv4 loopback is still present, though:</p>
<pre class="code highlight js-syntax-highlight plaintext" lang="plaintext" v-pre="true"><code><span id="LC1" class="line" lang="plaintext">eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500</span>
<span id="LC2" class="line" lang="plaintext"> inet6 2a02:16a8:dc41:100::240 prefixlen 64 scopeid 0x0<global></span>
<span id="LC3" class="line" lang="plaintext"> inet6 fe80::216:37ff:fed2:16f0 prefixlen 64 scopeid 0x20<link></span>
<span id="LC4" class="line" lang="plaintext"> ether 00:16:37:d2:16:f0 txqueuelen 1000 (Ethernet)</span>
<span id="LC5" class="line" lang="plaintext">[...]</span>
<span id="LC6" class="line" lang="plaintext">lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536</span>
<span id="LC7" class="line" lang="plaintext"> inet 127.0.0.1 netmask 255.0.0.0</span>
<span id="LC8" class="line" lang="plaintext"> inet6 ::1 prefixlen 128 scopeid 0x10<host></span>
<span id="LC9" class="line" lang="plaintext"> loop txqueuelen 1000 (Local Loopback)</span></code></pre>
<p dir="auto">However with this setup gnutls-serv only listens on the IPv6 interface:</p>
<p dir="auto">Adrian:</p>
<blockquote dir="auto">
<p>The conova buildds are IPv6-only, see #<a href="https://bugs.debian.org/962019" rel="nofollow noreferrer noopener" target="_blank">962019</a> for a similar problem in perl.</p>
</blockquote>
<p dir="auto">and in later message</p>
<blockquote dir="auto">
<p>The usage of AI_ADDRCONFIG in src/serv.c:listen_socket() looks similar to the problem described in the perl bug.</p>
</blockquote>
<p dir="auto">Julien:</p>
<blockquote dir="auto">
<p>And indeed gnutls-serv seems to call getaddrinfo with node == NULL and
hints.ai_flags == AI_PASSIVE|AI_ADDRCONFIG, to figure out what address
to listen on. If the host has no non-local ipv4 address, that
getaddrinfo call returns :: but not 0.0.0.0; and then the test hardcodes
127.0.0.1 as the address for gnutls-cli to connect to, and sadness
ensues.</p>
</blockquote>
</div>
</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #777;">
—
<br>
Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/-/issues/1007#note_356288765">view it on GitLab</a>.
<br>
You're receiving this email because of your account on gitlab.com.
If you'd like to receive fewer emails, you can
<a href="https://gitlab.com/-/sent_notifications/31a30a40fb54ee53223ddc9c0a1fa10a/unsubscribe">unsubscribe</a>
from this thread or
adjust your notification settings.
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Issue","url":"https://gitlab.com/gnutls/gnutls/-/issues/1007#note_356288765"}}</script>
</p>
</div>
</body>
</html>