IPv6 on update2.freebsd.org

Philip Paeps philip at freebsd.org
Sat Jul 31 02:17:22 UTC 2021


On 2021-07-31 07:40:19 (+0800), Dennis Radford wrote:

> On 7/30/2021 1:49 AM, Philip Paeps wrote:
>> On 2021-07-30 03:56:11 (+0800), Dennis Radford wrote:
>>> To whom it may concern,
>>>
>>> I just wanted to notify to proper individual(s) that IPv6 
>>> connectivity to
>>>
>>> Name:   update2.freebsd.org
>>> Address: 2620:11c:5001:1099:1337::117
>>>
>>> appears to have stopped working.
>>>
>>> Long delays running freebsd-update and does not respond to ping6 
>>> either. IPv6 on update.freebsd.org appears to be working normally. 
>>> Tested from 2 separate and dissimilar networks.
>>
>> Thanks for the report.  As far as I can tell, IPv6 is working fine 
>> on this mirror.  Can you please share a traceroute?
>>
>> Graham has helpfully created a bug for this.  I've assigned it to 
>> clusteradm now.
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257498
>>
>> Thanks.
>>
>> Philip
>>
> Sure thing.
>
>  traceroute6 to update2.freebsd.org (2620:11c:5001:1099:1337::117) 
> from 2002:b840:df6b:1::11, 64 hops max, 28 byte packets
>  1  2002:b840:df6b:1:da47:32ff:fe6c:75a8  0.345 ms  0.180 ms  0.150 ms
>  2  2002:c058:6301::1  28.439 ms  26.260 ms  26.769 ms
>  3  10gigabitethernet1-14.core1.sea1.he.net  26.981 ms  27.091 ms  
> 27.256 ms
>  4  v6-six2.metapeer.com  27.065 ms  27.316 ms  27.051 ms
>  5  2620:11c:5001:982::  36.566 ms  33.899 ms  33.846 ms
>  6  * * *
>  7  * * *
>
> Same results with traceroute6 on second separate network.
>
> - Dennis

Looks like metapeer simply doesn't have a route to 6to4 addresses.  It 
can get to your IPv4 address just fine though.

I don't know if this can be fixed.  I will ask.

Are you using 6to4 on purpose because you don't have native IPv6, or is 
there some configuration causing you to prefer 6to4 over native?

Philip

-- 
Philip Paeps
Senior Reality Engineer
Alternative Enterprises


More information about the freebsd-questions mailing list