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

[Christoph Egger]

Andrey Korobkov <address@hidden> writes:
> 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)?

works here:

2011-04-06 22:52:02 Requesting 30 missing keys from <ADDR_INET 
[2001:470:1f15:16f0::1:1137]:11371>, starting with 
4D852FC7D971194E481017D2D7D3AC65
2011-04-06 22:52:05 30 keys received

Regards

    Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer

A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?

pgp9ZD5pEvAh9.pgp
Description: PGP signature