sysupgrade.openwrt.org IPv6 appears dead

Goetz Goerisch ggoerisch at gmail.com
Fri Jun 28 07:03:19 PDT 2024


Hi all,

I did a measurement from RIPE Atlas anchors to
asu-01.infra.openwrt.org, as sysupgrade.openwrt.org CNAME resolution
fails sometimes:

https://atlas.ripe.net/measurements/74524089/overview

TL;DR not reachable from certain parts of the earth.

>From my traceroute, the digital ocean infrastructure does not respond
to ICMPv6 requests, which violates RFC4890.

Additionally the routing is asymmetric

 tracepath sysupgrade.openwrt.org
 1?: [LOCALHOST]                        0.016ms pmtu 1500
 1:  2a02:908:xxx:xxx::1                                 0.767ms
 1:  2a02:908:xxx:xxx::1                                 0.779ms
 2:  2a02:908:xxx:xxxx:xxxx:xxxx:xxxx:xxx1                1.407ms
 3:  2a02:908:xxx:5::1                                   12.764ms
 4:  7113a-mx960-01-ae10-1050.dar.unity-media.net         50.140ms
 5:  7113a-mx960-02.dar.unity-media.net                   12.959ms asymm  6
 6:  de-fra04d-rc1-lo0-0.v6.aorta.net                     13.427ms
 7:  telia-gw.fnt.cw.net                                  11.006ms
 8:  ffm-bb2-v6.ip.twelve99.net                           11.865ms asymm 10
 9:  digitalocean-ic-378009.ip.twelve99-cust.net          12.228ms asymm  8
10:  2a03:b0c0:fffe::68                                    9.688ms asymm  9
11:  2a03:b0c0:fffe::70                                   11.626ms asymm  9
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  asu-01.infra.openwrt.org                             12.240ms reached
     Resume: pmtu 1500 hops 17 back 14

 mtr sysupgrade.openwrt.org -z -6 -w
Start: 2024-06-28T16:01:34+0200
HOST:                                                  Loss%   Snt
Last   Avg  Best  Wrst StDev
  1. AS3209   2a02:908:xxx:xxx::1                          0.0%    10
  0.6   0.6   0.6   0.7   0.0
  2. AS3209   2a02:908:xxx:xxxx:xxxx:xxxx:xxxx:xxx1         0.0%    10
   1.3   1.4   1.0   2.0   0.4
  3. AS3209   2a02:908:xxx:5::1                             0.0%    10
   9.0  13.4   8.9  24.8   5.3
  4. AS3209   7113a-mx960-01-ae10-1050.dar.unity-media.net   0.0%
10   11.3  11.4   9.1  16.7   2.5
  5. AS3209   7113a-mx960-02.dar.unity-media.net             0.0%
10    9.5  12.3   8.4  22.2   4.2
  6. AS6830   de-fra04d-rc1-lo0-0.v6.aorta.net               0.0%
10   11.9  14.9   8.9  34.9   7.6
  7. AS1273   ae34-pcr1.fnt.cw.net                           0.0%
10    8.3  15.1   8.3  42.3  10.6
  8. AS???    ???                                           100.0
10    0.0   0.0   0.0   0.0   0.0
  9. AS1299   ffm-bb2-v6.ip.twelve99.net                     0.0%
10   15.0  11.9   8.3  17.4   3.0
 10. AS???    ???                                           100.0
10    0.0   0.0   0.0   0.0   0.0
 11. AS1299   digitalocean-ic-378009.ip.twelve99-cust.net    0.0%
10   11.6  12.0   8.5  17.8   3.5
 12. AS???    ???                                           100.0
10    0.0   0.0   0.0   0.0   0.0
 13. AS???    ???                                           100.0
10    0.0   0.0   0.0   0.0   0.0
 14. AS???    ???                                           100.0
10    0.0   0.0   0.0   0.0   0.0
 15. AS???    ???                                           100.0
10    0.0   0.0   0.0   0.0   0.0
 16. AS???    ???                                           100.0
10    0.0   0.0   0.0   0.0   0.0
 17. AS???    ???                                           100.0
10    0.0   0.0   0.0   0.0   0.0
 18. AS14061  asu-01.infra.openwrt.org                       0.0%
10   10.1  11.5   7.8  17.9   3.4

goetz

Am Do., 27. Juni 2024 um 02:32 Uhr schrieb Eric via openwrt-devel
<openwrt-devel at lists.openwrt.org>:
>
> 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.
>
>
> ---------- Forwarded message ----------
> From: Eric <evil.function at proton.me>
> To: Daniel Golle <daniel at makrotopia.org>
> Cc: noc at digitalocean.com, openwrt-devel <openwrt-devel at lists.openwrt.org>
> Bcc:
> Date: Thu, 27 Jun 2024 00:31:07 +0000
> Subject: Re: sysupgrade.openwrt.org IPv6 appears dead
> On Wednesday, June 26th, 2024 at 17:02, Daniel Golle <daniel at makrotopia.org> wrote:
>
> > Hi Eric,
> > Hi Digitalocean operators,
> >
> > On Wed, Jun 26, 2024 at 10:54:36PM +0000, Eric via openwrt-devel wrote:
> >
> > > [...]
> > > 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?
> >
> >
> > inet6num: 2a03:b0c0::/32
> > netname: US-DIGITALOCEANLLC-20121228
> > country: NL
> >
> > Something seems wrong with the route from twelve99 to our host at digitalocean,
> > as hop 12 is within DO network and our sysupgrade.openwrt.org box is hosted
> > with DO.
> >
> > Maybe Paul or someone with direct contact to DO can create a ticket there, I'm
> > not sure if sending an email to the noc@ address is enough.
> >
> >
> > Cheers
> >
> >
> > Daniel
>
> Appears to be working again:
>
> $ tracepath -6 2a03:b0c0:3:d0::1574:1
> ...
>  8:  nyk-bb1-v6.ip.twelve99.net                           89.371ms
>  9:  ldn-bb2-v6.ip.twelve99.net                          150.534ms asymm 11
> 10:  slou-b2-v6.ip.twelve99.net                          149.089ms
> 11:  digitalocean-ic-378006.ip.twelve99-cust.net         151.966ms
> 12:  2a03:b0c0:fffe::92                                  148.894ms
> 13:  no reply
> 14:  no reply
> 15:  no reply
> 16:  no reply
> 17:  asu-01.infra.openwrt.org                            170.037ms reached
>      Resume: pmtu 1500 hops 17 back 17
>
> Thanks everyone,
> Eric
>
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel



More information about the openwrt-devel mailing list