Hi!, We've prepared and set up a mirror for CentOS here at the IPN University. The relevant data next:
HTTP: http://mirror.cenac.ipn.mx/centos RSYNC: rsync://mirror.cenac.ipn.mx/centos FTP: N/A Sync frequency: hourly Located at: Nueva Industrial Vallejo?/CDMX/México BandWwidth: DOWN +/- 367.42 Mbps UP +/- 458.46 Mbps Sponsor organization: IPN (Instituto Politecnico Nacional) - http://www.ipn.mx
Let me know if you need some more info and when our mirror is finally plublished.
Thanks!
________________________________
La información de este correo así como la contenida en los documentos que se adjuntan, pueden ser objeto de solicitudes de acceso a la información. Visítanos: http://www.ipn.mx
DABDAI kirjoitti 9.11.2017 klo 22.00:
Hi!, We've prepared and set up a mirror for CentOS here at the IPN University. The relevant data next: HTTP: http://mirror.cenac.ipn.mx/centos RSYNC: rsync://mirror.cenac.ipn.mx/centos FTP: N/A Sync frequency: hourly Located at: Nueva Industrial Vallejo/CDMX/México BandWwidth: DOWN +/- 367.42 Mbps UP +/- 458.46 Mbps Sponsor organization: IPN (Instituto Politecnico Nacional) - http://www.ipn.mx Let me know if you need some more info and when our mirror is finally plublished. Thanks!
Hi, I have now added 148.204.14.246 to the ACL so you can now sync directly from rsync://us-msync.centos.org/CentOS/
I also set dabdai@ipn.mx as the contact email address for this mirror.
I'm afraid there are some problems with the rsync service:
$ rsync rsync://mirror.cenac.ipn.mx/centos/ rsync: failed to connect to mirror.cenac.ipn.mx (148.204.14.246): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9]
Although not a blocker, I had problems accessing IPN's website, possibly due to DNS problems. Both http://dnsviz.net/d/www.ipn.mx/dnssec/ and http://dnssec-debugger.verisignlabs.com/www.ipn.mx show some oddities. In addition:
$ dig @dns2.ipn.mx www.ipn.mx (waits a few seconds) dig: couldn't get address for 'dns2.ipn.mx': not found
It might be a good idea to verify that your DNS is set up correctly, preferably by testing the DNS setup from outside your own network.