sysupgrade.openwrt.org IPv6 appears dead

[Eric]

Sent with Proton Mail secure email.

On Wednesday, June 26th, 2024 at 15:00, Daniel Golle <daniel at makrotopia.org> wrote:

> Hi Eric,
> 
> On Wed, Jun 26, 2024 at 09:44:04PM +0000, Eric via openwrt-devel wrote:
> 
> > The sender domain has a DMARC Reject/Quarantine policy which disallows
> > sending mailing list messages using the original "From" header.
> > 
> > To mitigate this problem, the original message has been wrapped
> > automatically by the mailing list software.
> 
> > Date: Wed, 26 Jun 2024 21:44:04 +0000
> > From: Eric evil.function at proton.me
> > To: openwrt-devel openwrt-devel at lists.openwrt.org, Paul Spooren
> > mail at aparcar.org
> > Subject: sysupgrade.openwrt.org IPv6 appears dead
> > 
> > Maybe DNS isn't updating or something?
> > 
> > In any case, attempts to grab stuff from https://sysupgrade.openwrt.org are a crapshoot, depending on whether the client chooses the IPv4 or IPv6 address.
> > 
> > This 'wget' keeps retrying forever, while '-4' gets the file without pause.
> > 
> > $ wget -6 --connect-timeout=10 https://sysupgrade.openwrt.org/json/v1/overview.json
> > --2024-06-26 14:41:43-- https://sysupgrade.openwrt.org/json/v1/overview.json
> > Resolving sysupgrade.openwrt.org... 2a03:b0c0:3:d0::1574:1
> > Connecting to sysupgrade.openwrt.org|2a03:b0c0:3:d0::1574:1|:443... failed: Operation timed out.
> > Retrying.
> 
> 
> please check your IPv6 routing and firewall, it definitely works fine
> for me:
> 
> [daniel at box ~]$ wget -6 --connect-timeout=10 https://sysupgrade.openwrt.org/json/v1/overview.json
> --2024-06-26 22:53:54-- https://sysupgrade.openwrt.org/json/v1/overview.json
> Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
> Resolving sysupgrade.openwrt.org (sysupgrade.openwrt.org)... 2a03:b0c0:3:d0::1574:1
> Connecting to sysupgrade.openwrt.org (sysupgrade.openwrt.org)|2a03:b0c0:3:d0::1574:1|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 17634 (17K) [application/json]
> Saving to: ‘overview.json’
> 
> overview.json 100%[=========================================================================================================================================>] 17.22K --.-KB/s in 0.04s
> 
> 
> 2024-06-26 22:53:55 (449 KB/s) - ‘overview.json’ saved [17634/17634]
> 
> [daniel at box ~]$ tracepath -6 sysupgrade.openwrt.org
> 1?: [LOCALHOST] 0.013ms pmtu 1500
> 1: [privacy] 0.369ms
> 1: [privacy] 0.306ms
> 2: [privacy] 0.824ms asymm 1
> 3: [privacy]
> 4: [privacy] 4.474ms asymm 3
> 5: [privacy]
> 6: [privacy] 39.110ms asymm 5
> 7: fra2-edge1.digitalocean.com 38.661ms asymm 6
> 8: fra2-edge1.digitalocean.com 39.138ms asymm 6
> 9: no reply
> 10: no reply
> 11: no reply
> 12: no reply
> 13: no reply
> 14: asu-01.infra.openwrt.org 39.495ms reached
> Resume: pmtu 1500 hops 14 back 12
> 
> 
> Cheers
> 
> 
> Daniel

Hey Daniel,

Originally reported with this post on the forum https://forum.openwrt.org/t/owut-openwrt-upgrade-tool/200035/23.  I don't know the OP @cdes's geographic location.

Yeah, it's clearly a route issue, looks like after it crosses the Atlantic (that's usually when I see rtt jump from up to 150ms).  Those early ones are probably Los Angeles, as most of my traffic exits through there.

$ tracepath -6 2a03:b0c0:3:d0::1574:1
 1?: [LOCALHOST]                        0.015ms pmtu 1500
 1:  rtr00-br-lan.brain.lan                                4.688ms
 1:  rtr00-br-lan.brain.lan                                3.027ms
 2:  2600:8802:48ff:ffff::1111                            16.854ms
 3:  2001:578:400:7:f:0:2:8024                            14.782ms
 4:  2001:578:400:4:5000::32                              10.528ms
 5:  2001:578:1:0:172:17:249:32                           22.080ms
 6:  las-b23-link.ip.twelve99.net                         16.332ms
 7:  rest-bb1-v6.ip.twelve99.net                          69.931ms
 8:  nyk-bb2-v6.ip.twelve99.net                           78.901ms
 9:  ldn-bb1-v6.ip.twelve99.net                          151.764ms
10:  no reply
11:  digitalocean-ic-378007.ip.twelve99-cust.net         162.834ms
12:  2a03:b0c0:fffe::92                                  151.227ms
13:  no reply
... all no reply
30:  no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500

I seem to recall that twelve99 has a less than stellar reputation for this sort of issue...

How would one report such a problem?  Or do we just wait for the routing tables to get updated?

Eric