Re: [Savannah-hackers-public] Mirmon doesn't correctly report the status of rsync://netcologne.de/*

[Luke Yasuda]

On 2026-06-24 17:56, Roland Rosenfeld wrote:

Hi Ineiev!

On Di, 23 Jun 2026, Ineiev wrote:

rsync at download0 does download the file, but it takes
over 2 minutes; I wonder if it may be related to mixing addresses
194.8.197.22 and 2001:4dd0:1234:1::deb in the diagnostics:

That was a good hint.
There seems to be an issue with IPv6 via Hurricane Electric (he.net)
in combination with NetCologne.

I gave this to our network specialists...

HTTP/FTP seem to work without problems, because the client falls back
from IPv6 to IPv4, while the rsync client shows the issue.

Thanks for your reports, I'll hope, that it will be fixed soon...

I see issues when contacting sites with IPv6 via he.net from NetCologne.

traceroute6 from my dear personal VPS tuntun1.jing.rocks:

root@tuntun1:~# traceroute6 mirror.netcologne.de

 1  _gateway (2001:2c0:100:415::1)  0.695 ms  0.654 ms  0.623 ms

 8  * * *

10  * * *

12  * * *

20  * * *


traceroute6 from download0:

root@download0:~# traceroute6 mirror.netcologne.de

 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *^C
[...]

Cheers,
--
Luke Yasuda
GPG Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC

I can confirm that IPv6 from FSF Boston DC to mirror.netcologne.de does not work. ping6 shows 100% packet loss. IPv4 works fine. It certainly looks like a he.net-NetCologne peering issue from the output of traceroute6. I'm going to force mirror.netcologne.de to resolve to IPv4 in download0:/etc/hosts for now to mitigate the mirmon issue. traceroute to mirror.netcologne.de (2001:4dd0:1234:1::deb), 30 hops max, 80 byte packets 2 2001:2c0:100:414:17::1 (2001:2c0:100:414:17::1) 1405.715 ms 1405.686 ms 1405.668 ms 3 p215.v6.tky-kc-acr01.sphere.ad.jp (2001:2c0:0:6::95) 1.484 ms 1.893 ms 1.866 ms 4 0-0-0-20--2025.v6.tky-t3-fbdr01.sphere.ad.jp (2001:2c0:0:10::18) 1.957 ms 1.980 ms 2.647 ms 5 ix-et-3.hcore1.ovc-tokyo.ipv6.as6453.net (2001:5a0:2200:400::2d) 1.926 ms 7.865 ms 7.853 ms 6 if-bundle-55-2.qcore1.ovc-tokyo.ipv6.as6453.net (2405:2000:ff80::9) 1.673 ms 0.939 ms 0.939 ms 7 if-bundle-5-2.qcore2.ovc-tokyo.ipv6.as6453.net (2405:2000:ff80:120::3) 0.958 ms 1.243 ms 1.241 ms 9 if-bundle-16-2.qcore2.tv2-tokyo.ipv6.as6453.net (2405:2000:2502:10::c:47) 1.082 ms * * 11 * * if-bundle-6-2.qcore2.lvw-losangeles.ipv6.as6453.net (2405:2000:2d00::7) 109.684 ms 13 if-bundle-10-2.qcore1.nto-newyork.ipv6.as6453.net (2001:5a0:a00:100::6) 181.176 ms * * 14 * if-bundle-6-2.qcore1.n75-newyork.ipv6.as6453.net (2001:5a0:5702::10b) 183.975 ms * 15 2001:5a0:3900:100::7 (2001:5a0:3900:100::7) 182.253 ms 183.096 ms 180.455 ms 16 RT.NCL.CGN.DE.retn.net (2a02:2d8::57f5:e08e) 269.124 ms 267.612 ms 262.806 ms 17 GW-NetCologne.retn.net (2a02:2d8:3:1800:232a::1) 234.356 ms 237.711 ms 236.613 ms 18 ip-core-sto1-ae3.netcologne.de (2001:4dd0:a2b:e9:dc30::c) 235.126 ms ip-core-sto2-ae3.netcologne.de (2001:4dd0:a2b:ea:dc30::c) 231.370 ms ip-core-sto1-ae3.netcologne.de (2001:4dd0:a2b:e9:dc30::c) 238.083 ms 19 ip-core-kln2-et10-0-1.netcologne.de (2001:4dd0:a2b:207:dc80::1) 242.437 ms ip-core-kln2-et2-0-1.netcologne.de (2001:4dd0:a2b:206:dc80::1) 235.194 ms ip-core-kln2-et10-0-1.netcologne.de (2001:4dd0:a2b:207:dc80::1) 237.635 ms 21 mirror.netcologne.de (2001:4dd0:1234:1::deb) 240.961 ms 242.743 ms 234.634 ms traceroute to mirror.netcologne.de (2001:4dd0:1234:1::deb) from 2001:470:142:5::200, 30 hops max, 24 byte packets 1 gateway.coresite.gnu.org (2001:470:142::1) 0.26 ms 0.337 ms 0.247 ms 2 mass-ix.core1.bos1.he.net (2001:504:47::1b1b:0:1) 3.636 ms 4.875 ms 4.171 ms 3 be5.core3.lon5.he.net (2001:470:e:12b::2) 65.949 ms 66.292 ms 67.09 ms

signature.asc
Description: OpenPGP digital signature