Re: [Sks-devel] Are IPv6-only keyservers acceptable in the pool?

[Andrey Korobkov]

One more problem with IPv6 peering:

2011-04-07 00:23:44 address for keyserver.siccegge.de:11370 changed from [] to 
[<ADDR_INET [2001:a60:f01c:0:70:1:6:42]:11370>, <ADDR_INET [212
.114.250.148]:11370>, <ADDR_INET [212.114.250.149]:11370>]                      
                                                              
2011-04-07 00:23:44 address for keyserver.serviz.fr:11370 changed from [] to 
[<ADDR_INET [2a01:4f8:110:1283::c400]:11370>, <ADDR_INET [46.4.13
9.47]:11370>]
2011-04-07 00:24:44 Recon partner: <ADDR_INET [212.114.250.148]:11370>          
                                                              
2011-04-07 00:24:44 <recon as client> error in callback.: Unix error: Invalid 
argument - connect()                                            
2011-04-07 00:25:44 Recon partner: <ADDR_INET [46.4.139.47]:11370>              
                                                              
2011-04-07 00:25:44 <recon as client> error in callback.: Unix error: Invalid 
argument - connect()

Seems, that SKS uses IPv4 address for peering... Strange.
May be, it's because my SKS itself is listening on 127.0.0.1 and 
reverse-proxied via nginx?
What about your servers? Does IPv6-IPv6 peering work in such case (dual-stack)?

-- 
regards,
Andrey Korobkov         <address@hidden>
GPG Key: 
http://pool.sks-keyservers.net:11371/pks/lookup?search=0x177A2DB9EA08BF5D&fingerprint=on

pgpqnXeV4g8EA.pgp
Description: PGP signature