On 30/11/11 17:31, David Shaw wrote: >> Seems curl tries IPv4 then IPv6. >> >> mike@Fuzzbutt:~$ curl -v http://grepular.com:11371 >> * About to connect() to grepular.com port 11371 (#0) >> * Trying 178.79.145.246... Connection refused >> * Trying 2001:470:1f09:1186::beef... Failed to connect to >> 2001:470:1f09:1186::beef: Network is unreachable >> * Success >> * couldn't connect to host >> * Closing connection #0 >> curl: (7) Failed to connect to 2001:470:1f09:1186::beef: Network is >> unreachable > > Yes, but look at the error message. It matches what you saw from GnuPG. It > looks like libcurl tries the IPv4, fails, then the IPv6, and fails again. It > only displays an error message for the IPv6 as that was the last thing tried. > The keyserver handler uses libcurl as well, and is doing the same thing.
You're correct. tcpdump has confirmed that the initial attempt is done over IPv4. Still, the error message returned from gpg is misleading... -- Mike Cardwell https://grepular.com/ https://twitter.com/mickeyc Professional http://cardwellit.com/ http://linkedin.com/in/mikecardwell PGP.mit.edu 0018461F/35BC AF1D 3AA2 1F84 3DC3 B0CF 70A5 F512 0018 461F
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
