[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sks-devel] Problem with IPv6 detection in the pool?
From: |
Scott Grayban |
Subject: |
Re: [Sks-devel] Problem with IPv6 detection in the pool? |
Date: |
Sat, 28 May 2011 23:48:44 -0700 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.23) Gecko/20090812 Lightning/0.9.4-Inverse Thunderbird/2.0.0.23 Mnenhy/0.7.5.0 |
Looks like Sixxs is down.
$ tracepath6 keys.kfwebs.net
1?: [LOCALHOST] 0.058ms pmtu 1480
1: ipv6.borgnet.us 0.119ms pmtu 1472
1: ipv6.border.router 58.006ms
2: 2001:470:0:1f::1 57.525ms asymm 1
3: 10gigabitethernet1-2.core1.sjc2.he.net 62.349ms asymm 2
4: 10gigabitethernet3-3.core1.den1.he.net 84.829ms asymm 3
5: 10gigabitethernet1-1.core1.chi1.he.net 108.168ms asymm 4
6: 10gigabitethernet7-2.core1.nyc4.he.net 126.930ms asymm 5
7: 10gigabitethernet3-3.core1.lon1.he.net 203.040ms asymm 6
8: 2001:7f8:4::3f16:1 193.701ms asymm 7
9: te2-4-r71.cr0-r70.tc2-ams.nl.ip6.p80.net 202.015ms asymm 8
10: te2-2-r70.cr0-r72.gbl-cph.dk.ip6.p80.net 211.634ms asymm 9
11: te3-1-r72.cr0-r74.gbl-got.se.ip6.p80.net 220.195ms asymm 10
12: te4-2-r74.cr0-r65.hmg9-osl.no.ip6.p80.net 219.595ms asymm 11
13: 2001:16d8:3::2 220.972ms asymm 12
14: sixxs-oslo-demarc0.cust.ip6.p80.net 220.785ms asymm 13
15: sixxs-oslo-demarc0.cust.ip6.p80.net 221.389ms pmtu 1280
15: no reply
16: no reply
17: no reply
18: no reply
Regards,
Scott Grayban
/"\
\ / ASCII RIBBON
X FIGHT BREAST CANCER
/ \
Matthew Palmer said the following on 05/28/2011 11:25 PM:
> On Sun, May 29, 2011 at 01:16:25PM +1000, Matthew Palmer wrote:
>
>> I just noticed that keys.kfwebs.net is currently listed as the only
>> IPv6-capable keyserver in the status page at sks-keyservers.net/status.
>> Methinks something may have gone wrong there. As far as I can tell my
>> keyserver (sks.hezmatt.org) is still reachable via IPv6, and I suspect there
>> may be a problem in the IPv6 detection given that *everybody* has dropped
>> off.
>>
> Following up to myself, I noticed that pages off sks-keyservers.net were
> taking a while to load, and it seems to be because IPv6 connections are
> failing. Thus, my guess is that the "does IPv6 work?" code is based on a "can
> keys.kfwbs.net connect to it?" check, and keys.kfwebs.net has lost IPv6
> connectivity and hence everything else looks dead.
>
> A consequence of this is that pool.sks-keyservers.net is effectively dead
> over IPv6, since the only node in it is unreachable from (presumably) the
> rest of the world.
>
> - Matt
>
>