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

[Jim Spath <jspath55%gmail.com@localhost>]

Greg said:
>  I would expect that sysupgrade would at least try v6 and then v4 if v6 fails.

Yes, I observed this when I had an IPV4 only connection, The
sysupgrade fetch would try an IPv6 address, stall, then fall back to
IPv4.

I had hoped sysupgrade would behave like pkgin, which has flags to
omit 4 or 6 per request:

           -4               Forces to only use IPv4 addresses.
           -6               Forces to only use IPv6 addresses.

Alas, I have no clue how to make this so.

On Tue, Sep 29, 2026 at 7:29 AM Greg Troxel <gdt%lexort.com@localhost> wrote:
>
> [I agree with everything mouse@ said.]
> The next thing to check is if you have an IPv6 default route;
>
>    netstat -nr -f inet6
>
> and also to restart dhcpcd and look at the logs.
>
> On an arm device (to stay on topic :-) on my local network, there is a
> v6 address starting with 2001:  and a small last octet (assigned
> manally) and an address with the same prefix and a SLAAC
> (https://datatracker.ietf.org/doc/html/rfc4862) address where the bottom
> 64 are random or derived from the MAC addr.   I also have a fe80 link
> local address.
>
> I am guessing you have a v6 default route, do not have a global address,
> but have a site-local address -- which can be routed among systems on
> your site, if you had a lot of "links" aka Ethernet segments.
>
> I would examine the configuration of your router (that does dhcp and v6
> router adertisements) and also other computers.  Arguably it should not
> be configured to hand out site-local addresses, unless you understand
> the issues and want that.  IMHO wanting site-local addresses is unusual,
> and for experts.