NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: install/57864: Install first tries to load from cdn.netbsd.org using ipv6



The following reply was made to PR install/57864; it has been noted by GNATS.

From: Sergei K <sk757a%outlook.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: install/57864: Install first tries to load from cdn.netbsd.org
 using ipv6
Date: Thu, 18 Jan 2024 23:55:55 +0500

 On 18.01.2024 21:40, Martin Husemann wrote:
 >   7m is a strange value, I would have expected maximal 1m (per request).
 >   What does it do that long, can't be trying to connect to the non-reachable
 >   IPv6 address?
 >   
 >   Can you show the output of
 >   
 >   	host cdn.netbsd.org
 >   
 >   on your system?
 
 All clear
 
 > # host cdn.netbsd.org
 > cdn.netbsd.org is an alias for dualstack.o.ssl.global.fastly.net.
 > dualstack.o.ssl.global.fastly.net has address 151.101.85.6
 > dualstack.o.ssl.global.fastly.net has IPv6 address 2a04:4e42:70:262
 >
 > # host cdn.netbsd.org
 > cdn.netbsd.org is an alias for dualstack.o.ssl.global.fastly.net.
 > dualstack.o.ssl.global.fastly.net has address 151.101.85.6
 > dualstack.o.ssl.global.fastly.net has IPv6 address 2a84:4e42::262
 > dualstack.o.ssl.global.fastly.net has IPv6 address 2a04:4e42:200::262
 > dualstack.o.ssl.global.fastly.net has IPv6 address 2a84:4e42:400::262
 > dualstack.o.ssl.global.fastly.net has IPv6 address 2a84:4e42:600::262
 >
 > # host cdn.netbsd.org
 > cdn.netbsd.org is an alias for dualstack.o.ssl.global.fastly.net.
 > dualstack.o.ssl.global.fastly.net has address 146.75.1.6
 > dualstack.o.ssl.global.fastly.net has IPv6 address 2a04:4e42:14:262
 >
 > # host cdn.netbsd.org
 > cdn.netbsd.org is an alias for dualstack.o.ssl.global.fastly.net.
 > dualstack.o.ssl.global.fastly.net has address 151.101.85.6
 > dualstack.o.ssl.global.fastly.net has IPv6 address 2a04:4e42:14:262
 I also measured the running time of several runs of pkg_add (in s):
 > 77
 > 77
 > 302
 > 77
 > 77
 > 77
 > 302
 > 77
 > 77
 > 77
 The worst case (456 s) did not happen again. One might think that I was 
 simply mistaken, but since there is a photo of the screen, there is no 
 doubt :-)
 
 Well, thank you. The question can be closed now.
 



Home | Main Index | Thread Index | Old Index