Thank you.

Rsync schedule has been adjusted to every 4 hours.

I am also looking for IPv6 access to msync.centos.org .

-----原始邮件----- From: Fabian Arrotin Sent: Monday, November 10, 2014 2:52 AM To: centos-mirror@centos.org Subject: Re: [CentOS-mirror] CentOS mirror register :Shanghai Jiao TongUniversity

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 09/11/14 16:25, ????????? wrote:

Please consider adding our site to CentOS public mirror list.

HTTP: http://ftp.sjtu.edu.cn/centos/ FTP: ftp://ftp.sjtu.edu.cn/centos/

Sync schedule: Every 12 hrs Bandwidth: 1000Mbps Location: Shanghai, China Sponsor: Shanghai Jiao Tong University Sponsor URL: www.sjtu.edu.cn IP to authorize: 202.38.97.230 , 2001:da8:8000:6023::230 Email contact: colins@sjtu.edu.cn

Thanks : it has been added to the mirrors DB and will normally be listed as a public mirror (and on http://mirror-status.centos.org / http://centos.org/download/mirrors/ ) in the following hours. Your IP has been whitelisted (check that it's working in the following hour)

One (little) remark though : can you try to change your sync schedule to something smaller than 12hrs ?

Cheers,

- --

Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

_______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 06/11/14 08:23, sales@host-engine.com wrote:

Hello,

i have to send him my mirror's URL or the system will include them automatically?

thanks.

No, the ipv6 node producing the mirrorlist for ipv6 enabled machines uses the same list generated by mirror-status.centos.org, but verify/validate ipv6 connectivity and mirror content over ipv6. In your example, a "curl -6 'http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os&cc=u...'" shows already http://centos.host-engine.com/6/os/x86_64/ being included in the ipv6 enabled mirrors for .us :-)

Cheers,

- --

Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

6.11.2014, 18.15, sales@host-engine.com kirjoitti:

Hello,

i see in http://miuku.net/ipv6reach/ that i have mirrors that are not reachable from US, can you please provide me the US check ip to do a traceroute to it?

Hi, sorry, looks like I missed this message.

As of this writing, http://centos.chi.host-engine.com/ and http://centos.den.host-engine.com/ are unreachable from all four nodes, and http://centos.mia.host-engine.com/ is unreachable from the U.S. node.

centos.den.host-engine.com seems to have 15 IPv6 addresses listed, none of which are reachable. The reachability script tries all those IPv6 addresses with a 20 second timeout. The script will thus spend 5 minutes checking that particular mirror, because it can't connect to any of those IPv6 addresses.

The reachability script only tries to fetch TIME from the mirror, but the full script which checks if mirrors are up-to-date will retrieve repomd.xml for all architectures, all repos and all versions, for all listed IPv6 addresses. When centos.den.host-engine.com is reachable again, this script will download all those files 15 times every time a full check is needed. This is not really a problem for me, but I think it's a bit wasteful.

The reason I check all the addresses is that I've ran into mirrors that have multiple IPv6 addresses, of which only some work. All the IPv6 addresses listed in DNS for that mirror must work to get the mirror included on the IPv6 mirrorlist.

If you want to do traceroute6's, here are the IPv6 addresses (subject to change): FI: 2a01:51c0:1000:23:80:69:163:42 FR: 2001:4b98:dc0:41:216:3eff:fe69:46e3 UK: 2a02:2498:1:3d:5054:ff:feac:9450 US: 2600:3c01::f03c:91ff:fe69:9643

For other mirror admins reading this message: please check your mirror isn't listed as unreachable on http://miuku.net/ipv6reach/ , thank you.