ping doesn't seem to have an ip-version-agnostic setting. cabal could try both ping and ping6. Question is: Why does cabal even require ping? pinging a host is useful in network monitoring, but I have yet to see a situation where it is even helpful to establish a connection.
Good question! At the moment we donât have ipv6 enabled on our cdn â it looks like it was only recently made available to configure that way for general use [1]. Iâve talked to other admins, and I hope we can just turn on the switch and have it work going forward. Until then, hereâs the ipv6 address of the current origin hackage server, which can perhaps be used in the meantime?
2001:4800:7821:103:be76:4eff:fe04:b11a
[1]Â https://www.fastly.com/blog/ipv6-fastly
Cheers, Gershom
On April 26, 2017 at 5:43:37 PM, Serguey Zefirov (sergueyz@gmail.com) wrote:
I have found that Cabal does not work on IPv6-only networks (which my machine happen to be part of).
The problem is basically this: "ping hackage.haskell.org" does not resolve host while "ping6 hackage.haskell.org" does. Thus cabal cannot do anything useful on that machine.
Do anyone have a solution for that? I was unable to find any on the internet. ;) _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.