On 25 January 2015 at 00:10, Andy Bradford <amb-fos...@bradfords.org> wrote: > Thus said Richard Hipp on Sat, 24 Jan 2015 16:27:55 -0500: > >> I would hope that the local machine knows that it cannot provide IPv6 >> service and that getaddrinfo() should therefore always return an IPv4 >> address. But apparently that is not happening on Michai's machine. > > That's a fair point. I don't have to do anything special and I'm still > able to clone. So clearly some OSes are able to ignore the AAAA record. > > I suspect that he may actually have IPv6 enabled without realizing it.
I think that's right; the choice to configure IPv6 routing for instance is based (here) on whether the kernel has support for IPv6, from what I can see. > If their OS is configured correctly, it should ``just work'' but there > may be other circumstances (e.g. they have IPv6 configured for local > networks, but no access to IPv6 on the Internet, so their OS may > actually think it wants to do IPv6 and it may actually prefer it if it > finds an AAAA record (Microsoft Windows is this way. If it has IPv6 > enabled and there is an AAAA record for the host, it will always prefer > IPv6). I think that's exactly what's happening; other userland tools try IPv6, and seeing that fails, give up: michai@delle:~$ ftp ftp.netbsd.org Trying 2001:470:a085:999::21:21 ... ftp: Can't connect to `2001:470:a085:999::21:21': No route to host Trying 199.233.217.226:21 ... Connected to ftp.netbsd.org. Arguably this is a misconfiguration on my machine. I haven't really given it any attention yet, tbh. Michai _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
