Re: NetBSD-Archive down?

Malte Dehling <mdehling%gmail.com@localhost> writes:

> On Fri 15. Apr 2022 at 10:12, Greg Troxel <gdt%lexort.com@localhost> wrote
> offlist which was then later copied to the list:
>
>> Malte Dehling <mdehling%gmail.com@localhost> writes:
>>
>> > I have been trying to access the NetBSD archives at
>> > https://archive.netbsd.org/ but keep getting an error 503 - first byte
>> > timeout. Is that server currently unavailable? Anywhere else I might be
>> > able to download older NetBSD install media?
>>
>> also works for me, northeast US
>
> Allright, so I got what I needed by going through a VPN. That doesn’t
> solve the issue, though. I’m not sure who needs to see this to get the
> server fixed?

Well, for starters you need to provide a lot more information.

Then, you or others could begin to speculate about where the problem is.
Asserting that the server is broken is quite a leap, even though it
certainly could be.

Not much of a leap considering 503 is a server error. The message seems to indicate a timeout in the connection from the CDN to the regional server.

So:

What country are you in?

I mentioned that: southern california.

In what IPv4 prefix is your v4 address?

public IP is 76.88.x.x

Same for v6.

Is this problem with v4, v6, both?

I’m not using ipv6.

When you do "dig archive.netbsd.org in a" (and aaaa) what address do
you get?

# dig archive.netbsd.org in a

; <<>> DiG 9.16.20 <<>> archive.netbsd.org in a

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30279

;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;archive.netbsd.org. IN A

;; ANSWER SECTION:

archive.netbsd.org. 1603 IN CNAME dualstack.o.ssl.global.fastly.net.

dualstack.o.ssl.global.fastly.net. 30 IN A 151.101.1.6

dualstack.o.ssl.global.fastly.net. 30 IN A 151.101.65.6

dualstack.o.ssl.global.fastly.net. 30 IN A 151.101.129.6

dualstack.o.ssl.global.fastly.net. 30 IN A 151.101.193.6

;; Query time: 22 msec

;; SERVER: 192.168.86.1#53(192.168.86.1)

;; WHEN: Fri Apr 15 10:51:50 PDT 2022

;; MSG SIZE rcvd: 158

What happens when you traceroute/traceroute6 to those addresses?

# traceroute archive.netbsd.org

traceroute: archive.netbsd.org has multiple addresses; using 151.101.1.6

traceroute to dualstack.o.ssl.global.fastly.net (151.101.1.6), 64 hops max, 40 byte packets

1 192.168.86.1 (192.168.86.1) 7.428 ms 2.339 ms 4.639 ms

2 142-254-184-149.inf.spectrum.com (142.254.184.149) 13.814 ms 6.607 ms 9.953 ms

3 lag-63.sndhcaht01h.netops.charter.com (76.167.26.105) 23.129 ms 30.346 ms 32.246 ms

4 lag-21.sndhcaax01r.netops.charter.com (72.129.1.54) 14.918 ms 17.794 ms 16.223 ms

5 lag-22.lsancarc01r.netops.charter.com (72.129.1.0) 17.757 ms 16.020 ms 14.493 ms

6 lag-46.lsancarc0yw-bcr00.netops.charter.com (209.18.43.62) 16.508 ms

lag-16.lsancarc0yw-bcr00.netops.charter.com (66.109.6.102) 16.794 ms

lag-36.lsancarc0yw-bcr00.netops.charter.com (66.109.6.92) 17.578 ms

7 lag-0.pr2.lax00.netops.charter.com (66.109.5.123) 17.404 ms 19.137 ms

lag-800.pr2.lax00.netops.charter.com (66.109.7.225) 22.625 ms

8 * * *

When you run tcpdump to watch a connection attempt, what do you see?

# tcpdump tcp

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on genet0, link-type EN10MB (Ethernet), capture size 262144 bytes

11:05:38.645434 IP 192.168.86.2.65531 > 151.101.1.6.http: Flags [S], seq 2059843661, win 32768, options [mss 1460,nop,wscale 3,sackOK,TS val 1 ecr 0], length 0

11:05:38.661713 IP 151.101.1.6.http > 192.168.86.2.65531: Flags [S.], seq 763067123, ack 2059843662, win 65535, options [mss 1460,sackOK,TS val 457835305 ecr 1,nop,wscale 9], length 0

11:05:38.661757 IP 192.168.86.2.65531 > 151.101.1.6.http: Flags [.], ack 1, win 4197, options [nop,nop,TS val 1 ecr 457835305], length 0

11:05:38.661860 IP 192.168.86.2.65531 > 151.101.1.6.http: Flags [P.], seq 1:27, ack 1, win 4197, options [nop,nop,TS val 1 ecr 457835305], length 26: HTTP: GET /index.html HTTP/1.1

11:05:38.685981 IP 151.101.1.6.http > 192.168.86.2.65531: Flags [.], ack 27, win 283, options [nop,nop,TS val 457835329 ecr 1], length 0

11:05:38.686058 IP 192.168.86.2.65531 > 151.101.1.6.http: Flags [P.], seq 27:120, ack 1, win 4197, options [nop,nop,TS val 1 ecr 457835329], length 93: HTTP

11:05:38.701592 IP 151.101.1.6.http > 192.168.86.2.65531: Flags [.], ack 120, win 283, options [nop,nop,TS val 457835345 ecr 1], length 0

11:05:54.454763 IP 151.101.1.6.http > 192.168.86.2.65531: Flags [P.], seq 1:339, ack 120, win 283, options [nop,nop,TS val 457851097 ecr 1], length 338: HTTP: HTTP/1.1 503 first byte timeout

11:05:54.454777 IP 151.101.1.6.http > 192.168.86.2.65531: Flags [P.], seq 339:794, ack 120, win 283, options [nop,nop,TS val 457851097 ecr 1], length 455: HTTP

11:05:54.454781 IP 151.101.1.6.http > 192.168.86.2.65531: Flags [F.], seq 794, ack 120, win 283, options [nop,nop,TS val 457851097 ecr 1], length 0

11:05:54.454834 IP 192.168.86.2.65531 > 151.101.1.6.http: Flags [.], ack 794, win 4098, options [nop,nop,TS val 33 ecr 457851097], length 0

11:05:54.454858 IP 192.168.86.2.65531 > 151.101.1.6.http: Flags [.], ack 795, win 4098, options [nop,nop,TS val 33 ecr 457851097], length 0

11:05:54.456161 IP 192.168.86.2.65531 > 151.101.1.6.http: Flags [F.], seq 120, ack 795, win 4197, options [nop,nop,TS val 33 ecr 457851097], length 0

11:05:54.476748 IP 151.101.1.6.http > 192.168.86.2.65531: Flags [.], ack 121, win 283, options [nop,nop,TS val 457851121 ecr 33], length 0