IPv6 failover?

Jason Harris jharris at widomaker.com
Thu Aug 4 02:18:35 CEST 2005


On Wed, Aug 03, 2005 at 07:25:41PM -0400, David Shaw wrote:

> The thing is, if you have a --with-libcurl build, this failover would
> need to happen within curl itself.  What happens if you do:
>   curl http://keyserver.linux.it:11371/pks/add
> 
> on the command line.  Obviously it won't do anything keyserver-wise,
> but does it manage to connect?

It does:

  %curl -v http://keyserver.linux.it:11371/pks/add
  * About to connect() to keyserver.linux.it port 11371
  *   Trying 2001:1418:13:10::1... Failed to connect to 2001:1418:13:10::1: No route to host
  * Undefined error: 0
  *   Trying 62.94.26.10... connected
  * Connected to keyserver.linux.it (62.94.26.10) port 11371
  [snip]

Looking at http://curl.haxx.se/libcurl/c/curl_easy_setopt.html ,
this might do the trick:

  curl_easy_setopt (..., CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4); 

if any connection, which always seems to prefer IPv6, doesn't
at first succeed.

-- 
Jason Harris           |  NIC:  JH329, PGP:  This _is_ PGP-signed, isn't it?
jharris at widomaker.com _|_ web:  http://keyserver.kjsl.com/~jharris/
          Got photons?   (TM), (C) 2004
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 313 bytes
Desc: not available
Url : /pipermail/attachments/20050803/15fba6c9/attachment.pgp


More information about the Gnupg-users mailing list