Re: [Sks-devel] IPv6 configuration error

[David Benfell]

On Sun, 10 Apr 2011, C.J. Adams-Collier wrote:

> But then it works... sometimes:
> 
> address@hidden:~$ gpg --keyserver [2001:470:a:233:9::29] --recv-keys 
> 0xba27a83c
> gpg: requesting key BA27A83C from hkp server [2001:470:a:233:9::29]
> gpg: keyserver timed out
> gpg: keyserver receive failed: keyserver error
> address@hidden:~$ gpg --keyserver [2001:470:a:233:9::29] --recv-keys 
> 0xba27a83c
> gpg: requesting key BA27A83C from hkp server [2001:470:a:233:9::29]
> gpg: key BA27A83C: "C.J. Adams-Collier <address@hidden>" not changed
> gpg: Total number processed: 1
> gpg:              unchanged: 1
> 
> I should probably go to sleep and think about it when it's not 4 in
> the morning...

Rats.  And I've dropped out of the pool due to missing keys, so I'm
guessing you're not the only one.  But I'm also seeing it with IPv4:

2011-04-10 05:29:45 Requesting 3 missing keys from <ADDR_INET 
[208.84.222.190]:11371>, starting with 1DA31FDDBCA842F6BBD2DA91EAAFF6BD
2011-04-10 05:29:45 3 keys received
2011-04-10 05:29:46 Added 3 hash-updates. Caught up to 1302438585.772271
2011-04-10 05:31:32 <recon as client> callback timed out.
2011-04-10 05:33:19 <recon as client> callback timed out.
2011-04-10 05:36:10 Hashes recovered from <ADDR_INET [84.45.72.144]:11371>
2011-04-10 05:36:10     1787DCD39699985F472E7EDAD33E2710
2011-04-10 05:36:20 Requesting 1 missing keys from <ADDR_INET 
[84.45.72.144]:11371>, starting with 1787DCD39699985F472E7EDAD33E2710
2011-04-10 05:36:20 1 keys received
2011-04-10 05:36:21 Added 1 hash-updates. Caught up to 1302438980.831585
2011-04-10 05:37:36 <recon as client> error in callback.: Unix error: 
Connection timed out - connect()
2011-04-10 05:38:39 Hashes recovered from <ADDR_INET [161.53.2.219]:11371>
2011-04-10 05:38:39     4E9C89B0399EF82D1DAE9D8F23EA8F3E
2011-04-10 05:38:40 Requesting 1 missing keys from <ADDR_INET 
[161.53.2.219]:11371>, starting with 4E9C89B0399EF82D1DAE9D8F23EA8F3E
2011-04-10 05:38:40 1 keys received
2011-04-10 05:38:41 Added 1 hash-updates. Caught up to 1302439121.009388
2011-04-10 05:40:26 <recon as client> callback timed out.
2011-04-10 05:42:09 <recon as client> callback timed out.
2011-04-10 05:44:26 <recon as client> error in callback.: Unix error: 
Connection timed out - connect()
2011-04-10 05:46:13 <recon as client> callback timed out.
2011-04-10 05:46:13 Hashes recovered from <ADDR_INET 
[2a01:4f8:100:2ffe::2]:11371>
2011-04-10 05:46:13     FCDBB2D56731B8C9D71D4579EA4BD6E5
2011-04-10 05:46:18 Reconciliation attempt from <ADDR_INET 
[84.45.72.144]:56352> while gossip disabled. Ignoring.
2011-04-10 05:46:23 Requesting 1 missing keys from <ADDR_INET 
[2a01:4f8:100:2ffe::2]:11371>, starting with FCDBB2D56731B8C9D71D4579EA4BD6E5
2011-04-10 05:46:23 1 keys received
2011-04-10 05:46:24 Added 1 hash-updates. Caught up to 1302439583.922810
2011-04-10 05:50:41 <recon as client> error in callback.: Unix error: 
Connection timed out - connect()
2011-04-10 05:53:44 <recon as client> error in callback.: Unix error: 
Connection refused - connect()
2011-04-10 05:54:00 Hashes recovered from <ADDR_INET [188.40.47.54]:11371>
2011-04-10 05:54:00     AD321321835C75BD3105FD51030D434E
2011-04-10 05:54:00     D52D51D8D90EF64E2D91A5C662FB55BE

I'm guessing that at least for me, this is not an IPv6 problem.  Is
that reasonable?

-- 
David Benfell <address@hidden>
http://www.parts-unknown.org/

signature.asc
Description: Digital signature