On 2020-11-20 16 h 01, Philip Paeps wrote: > On 2020-11-20 14:34:28 (+0100), Claude Buisson wrote: >> On 2020-11-20 12 h 38, David Wolfskill wrote: >>> On Fri, Nov 20, 2020 at 11:51:32AM +0100, Claude Buisson wrote: >>>> Hello, >>>> >>>> $ svnsync sync file:///home/svnmirror/base >>>> svnsync: E170013: Unable to connect to a repository at URL >>>> 'https://svn.freebsd.org/base' >>>> svnsync: E000065: Error running context: No route to host >>>> >>>> $ host svn.freebsd.org >>>> svn.freebsd.org is an alias for svnmir.geo.freebsd.org. >>>> svnmir.geo.freebsd.org has address 213.138.116.72 >>>> svnmir.geo.freebsd.org has IPv6 address 2001:41c8:112:8300::e6a:0 >>>> svnmir.geo.freebsd.org mail is handled by 0 . >>>> >>>> $ svnsync sync file:///home/svnmirror/base >>>> https://213.138.116.72:443/base >>>> Error validating server certificate for 'https://213.138.116.72:443': >>>> - The certificate hostname does not match. >>>> Certificate information: >>>> - Hostname: svn.freebsd.org >>>> - Valid: from Oct 17 20:29:49 2020 GMT until Jan 15 20:29:49 2021 GMT >>>> - Issuer: Let's Encrypt Authority X3, Let's Encrypt, US >>>> - Fingerprint: >>>> 0C:6D:4D:AF:97:EB:B4:EC:94:F3:8C:E2:BD:9F:E8:8C:C8:CF:15:81 >>>> (R)eject, accept (t)emporarily or accept (p)ermanently? t >>>> >>>> idem ports,doc >>>> >>>> CBu >>>> .... >>> >>> I don't see that; indeed, I just updated my local private mirrors >>> without issue. DNS resolution from here: >>> >>> g1-48(12.2-S)[1] host svn.freebsd.org >>> svn.freebsd.org is an alias for svnmir.geo.freebsd.org. >>> svnmir.geo.freebsd.org has address 96.47.72.69 >>> svnmir.geo.freebsd.org has IPv6 address 2610:1c1:1:606c::e6a:0 >>> svnmir.geo.freebsd.org mail is handled by 0 . >>> g1-48(12.2-S)[2] >>> >>> Peace, >>> david >>> >> >> It looks like the problem is linked to IPv6: >> >> $ svnsync sync file:///home/svnmirror/base >> https://[2001:41c8:112:8300::e6a:0]:443/base >> svnsync: E170013: Unable to connect to a repository at URL >> 'https://[2001:41c8:112:8300::e6a:0]/base' >> svnsync: E000065: Error running context: No route to host > > Errr ... I upgraded the bme svn mirror recently. I checked that svn > still worked but I'm not sure if I checked ipv6 and legacy ip > individually. I'll go and double-check ipv6. > > Thanks for pointing this out. Sorry for breaking it. > > Dogfood so tasty. > > Philip [clusteradm pointy hat collector] > It seems that the problem was the consequence of some bad IPv6 routing by my ISP. After many useless tests of my local gear, everything is back to normal. Thanks for your interest ! CBuReceived on Fri Nov 20 2020 - 15:27:57 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:25 UTC