pkg update

[Jos Chrispijn]

Recently I experience pkg upgrade/update lasts 20 minutes before the command is accepted/processed
Using -4 works though. Is it due to an IPv6 issue on the hosting side?
regards
./jos

[Jos Chrispijn]

[Marco Moock]

Am 21.04.26 um 10:26 schrieb Jos Chrispijn:

> Using -4 works though. Is it due to an IPv6 issue on the hosting side?

IPv6 works just fine for me. Please check if your name resolution is
working find and if you can reach the servers.

For me, it returns the following:
pkgmir.geo.freebsd.org has IPv6 address 2a04:4e42:400::497
pkgmir.geo.freebsd.org has IPv6 address 2a04:4e42:200::497
pkgmir.geo.freebsd.org has IPv6 address 2a04:4e42::497
pkgmir.geo.freebsd.org has IPv6 address 2a04:4e42:600::497

The result might be different for you, so test the result you get and
try to ping those machines.

If that doesn't work, investigate the network issue.

--
Gruß
Marco

Junk-Mail bitte an tras...@stinkedores.dorfdsl.de

[Pete Wright]

i haven't observed any issues using ipv6 directly, nor with dual-stack
setups. i assume you can hit other ipv6 sites and "ping6
pkg.freebsd.org" look ok on your end?

-p

--
Pete Wright
pe...@nomadlogic.org

[Marco Moock]

Am 21.04.26 um 19:50 schrieb Pete Wright:

>
> i haven't observed any issues using ipv6 directly, nor with dual-stack
> setups.  i assume you can hit other ipv6 sites and "ping6
> pkg.freebsd.org" look ok on your end?

I am able to reach the repo via IPv6 properly.

--
Gruß
Marco
Muell und Spam bitte an abfalle...@stinkedores.dorfdsl.de

[Jos Chrispijn]

Pete Wright:

> i haven't observed any issues using ipv6 directly, nor with dual-stack
> setups.  i assume you can hit other ipv6 sites and "ping6
> pkg.freebsd.org" look ok on your end?

PING(56=40+8+8 bytes) 2a10:3781:44a3:1::54 --> 2a04:4e42:200::497

(0nly one line)

--- pkgmir.geo.freebsd.org ping statistics ---
14 packets transmitted, 0 packets received, 100.0% packet loss

./jos

[Marco Moock]

Am 21.04.26 um 21:54 schrieb Jos Chrispijn:

It seems that this machine does not reply to ICMP echo request (and does
not reject, but drops them)

The pkg software asks for the SRV record of pkg.FreeBSD.org.

~$ dig srv pkg.FreeBSD.org +short
pkgmir.geo.FreeBSD.org.
~$

Then the A/AAAA record will be used to connect to this hostname.

[John Levine]

It appears that Marco Moock <m...@dorfdsl.de> said:
>
>The pkg software asks for the SRV record of pkg.FreeBSD.org.
>
>~$ dig srv pkg.FreeBSD.org +short
>pkgmir.geo.FreeBSD.org.

Actually, that's a CNAME. There's no SRV record. But I agree it works
fine over IPv6.

$ dig pkg.freebsd.org aaaa

; <<>> DiG 9.10.6 <<>> pkg.freebsd.org aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43317
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;pkg.freebsd.org. IN AAAA

;; ANSWER SECTION:
pkg.freebsd.org. 248 IN CNAME pkgmir.geo.freebsd.org.
pkgmir.geo.freebsd.org. 150 IN AAAA 2610:1c1:1:606c::50:1

[Philip Paeps]

It looks like you have an IPv6 problem. I can reach 2a04:4e42:200::497
fine from here.

This is one of the Fastly caches. Are you able to reach other Fastly
infrastructure over IPv6? (Or anything at all over IPv6 for that
matter.)

Philip

[Marco Moock]

Am 22.04.26 um 07:43 schrieb Philip Paeps:

> On 2026-04-22 03:54:34 (+0800), Jos Chrispijn wrote:
>> Pete Wright:
>>> i haven't observed any issues using ipv6 directly, nor with dual-
>>> stack setups.  i assume you can hit other ipv6 sites and "ping6
>>> pkg.freebsd.org" look ok on your end?
>>
>> PING(56=40+8+8 bytes) 2a10:3781:44a3:1::54 --> 2a04:4e42:200::497
>>
>> (0nly one line)
>>
>> --- pkgmir.geo.freebsd.org ping statistics ---
>> 14 packets transmitted, 0 packets received, 100.0% packet loss
>
> It looks like you have an IPv6 problem.  I can reach 2a04:4e42:200::497
> fine from here.

The IP Jos got is different and from another ISP. I can reach fastly
too, but 2a10:3781:44a3:1::54 does not reply to ICMP echo requests, but
traceroute shows it goes into their network.

[Jos Chrispijn]

Philip Paeps:

> It looks like you have an IPv6 problem.  I can reach 2a04:4e42:200::497
> fine from here.

Yes that's what I think as well. The issue is with server2server traffic.

> This is one of the Fastly caches.  Are you able to reach other Fastly
> infrastructure over IPv6?  (Or anything at all over IPv6 for that matter.)

I am not familiar with Fastly caches.
I am working with fiber connection to ISP through a wholesale fiber
provider.

./jos