Re: sysupgrade can't reach nycdn.netbsd.org

[Ted Spradley <tsprad%talent-free-studios.com@localhost>]

On Mon, 28 Sep 2026 18:56:22 -0400
Greg Troxel <gdt%lexort.com@localhost> wrote:

> ping6 nycdn.netbsd.org
> ping nycdn.netbsd.org
> 
> and then traceroute6/traceroute to the same name.
> 
> You might also see if you have a global v6 address, how you got that,
> what the default route is.

Script started on Mon Sep 28 22:01:19 2026
netop$ ping -c 5 nycdn.netbsd.org
PING dualstack.o.ssl.global.fastly.net (151.101.161.6): 56 data bytes
64 bytes from 151.101.161.6: icmp_seq=0 ttl=56 time=2.785376 ms
64 bytes from 151.101.161.6: icmp_seq=1 ttl=56 time=2.858000 ms
64 bytes from 151.101.161.6: icmp_seq=2 ttl=56 time=2.695544 ms
64 bytes from 151.101.161.6: icmp_seq=3 ttl=56 time=2.770209 ms
64 bytes from 151.101.161.6: icmp_seq=4 ttl=56 time=3.337493 ms

----dualstack.o.ssl.global.fastly.net PING Statistics----
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.695544/2.889324/3.337493/0.257090 ms
netop$ netop$ ping6 -c 5 nycdn.netbsd.org
PING6(56=40+8+8 bytes) fdc7:8cef:197:4:a39d:5a7c:6b2a:cdeb -->
2a04:4e42:26::262

--- dualstack.o.ssl.global.fastly.net ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
netop$ traceroute6 nycdn.netbsd.org
traceroute6 to dualstack.o.ssl.global.fastly.net (2a04:4e42:26::262)
from fdc7:8cef:197:4:a39d:5a7c:6b2a:cdeb, 64 hops max, 12 byte packets
1  fdc7:8cef:197:4:c256:27ff:fe6d:a283  0.36 ms  0.253 ms  0.223 ms 2
* * * 3  * * *
 4  * * *
 5  * * *
[...]
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
^C
netop$ traceroute nycdn.netbsd.org
traceroute to dualstack.o.ssl.global.fastly.net (151.101.113.6), 64
hops max, 40 byte packets 1  dmz (10.0.0.5)  0.192 ms  0.177 ms  0.182
ms 2  192.168.1.254 (192.168.1.254)  0.937 ms  0.641 ms  0.468 ms
 3  108-226-140-1.lightspeed.rcsntx.sbcglobal.net (108.226.140.1)
1.078 ms  1.177 ms  0.978 ms 4  71.155.13.16 (71.155.13.16)  1.994 ms
2.029 ms  2.015 ms 5  12.242.112.52 (12.242.112.52)  2.476 ms  2.571
ms  2.432 ms 6  * * *
 7  * * *
 8  * * *
 9  * * *
[...]
39  * * *
40  *^C
netop$ 

Script done on Mon Sep 28 22:27:30 2026

also:

rge0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        capabilities=0x3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
        capabilities=0x3f00<UDP4CSUM_Rx,UDP4CSUM_Tx>
        enabled=0
        ec_capabilities=0x3<VLAN_MTU,VLAN_HWTAGGING>
        ec_enabled=0
        address: c0:74:2b:fe:69:63
        media: Ethernet autoselect (1000baseT full-duplex)
        status: active
        inet6 fe80::c274:2bff:fefe:6963%rge0/64 flags 0 scopeid 0x1
        inet6 fdc7:8cef:197:4:a39d:5a7c:6b2a:cdeb/64 flags
0x40<AUTOCONF>
	inet 10.0.0.118/24 broadcast 10.0.0.255 flags 0
        inet 169.254.231.221/16 broadcast 169.254.255.255 flags 0

I still haven't get my head wrapped around IPv6 addressing (I'm an old
man). Should I have a 3rd IPv6 address that starts with a 2?


-- 
Ted Spradley <tsprad%talent-free-studios.com@localhost>