Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 908566 - rsync over IPv6 times out, only succeeds when it falls back to IPv4
Summary: rsync over IPv6 times out, only succeeds when it falls back to IPv4
Status: RESOLVED INVALID
Alias: None
Product: Mirrors
Classification: Unclassified
Component: Server Problem (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Mirror Admins
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-16 05:47 UTC by Bob Deblier
Modified: 2023-08-11 20:08 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bob Deblier 2023-06-16 05:47:06 UTC
emerge --sync first tries to contact a mirror over IPv6, times out, tries a second one over IPv6, times out, and only succeeds when the third try uses an IPv4 address:

>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
 * Using keys from /usr/share/openpgp-keys/gentoo-release.asc
 * Refreshing keys via WKD ...                                           [ ok ]
>>> Starting rsync with rsync://[2a00:1828:a00d:ffff::6]/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [Receiver=3.2.7]
>>> Retrying...


>>> Starting retry 1 of 3 with rsync://[2a01:90:200:10::1a]/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [Receiver=3.2.7]
>>> Retrying...


>>> Starting retry 2 of 3 with rsync://81.91.253.252/gentoo-portage
>>> Checking server timestamp ...
Welcome to starling.gentoo.org / rsync.gentoo.org

Server Address : 81.91.253.252, 2a01:90:200:10::1a
Contact Name   : mirror-admin@gentoo.org
Hardware       : 2 x Intel(R) Xeon(R) CPU E5-2470 0 @ 2.30GHz, 3946MB RAM
Sponsor        : Qube Managed Services Limited, Zurich, Switzerland, EU
Comment 1 Bob Deblier 2023-08-11 20:08:06 UTC
Root of the problem was in the modem / router that my ISP provided.