Hi fellow mirror admins.
I made a list of mirrors that have a published AAAA record, and checked if those mirrors are actually reachable by IPv6. Unfortunately it looks like there is a significant amount of mirrors that do have an AAAA record, but the actual services (http, ftp, rsync) are not available by IPv6.
Here is the list:
FAIL: http://mirrors.arsc.edu/centos/ FAIL: ftp://mirrors.arsc.edu/centos/ OK: http://linux.mirrors.es.net/centos/ OK: ftp://linux.mirrors.es.net/centos/ OK: rsync://linux.mirrors.es.net/linux-pub/ OK: http://mirrors.loosefoot.com/centos/ OK: ftp://mirrors.loosefoot.com/centos/ OK: rsync://mirrors.loosefoot.com/centos/ OK: http://ftp.usf.edu/pub/centos/ OK: ftp://ftp.usf.edu/pub/centos/ OK: http://www.gtlib.gatech.edu/pub/centos/ OK: ftp://ftp.gtlib.gatech.edu/pub/centos/ OK: rsync://rsync.gtlib.gatech.edu/centos/ OK: http://mirror.ancl.hawaii.edu/linux/centos/ OK: http://mirrors.syringanetworks.net/centos/ OK: ftp://mirrors.syringanetworks.net/centos/ OK: rsync://mirrors.syringanetworks.net/centos/ OK: http://mirror.anl.gov/pub/centos/ OK: ftp://mirror.anl.gov/pub/centos/ OK: rsync://mirror.anl.gov/centos/ OK: http://mirror.fdcservers.net/centos/ FAIL: ftp://mirror.fdcservers.net/centos/ OK: http://mirrors.gigenet.com/centos/ OK: ftp://mirrors.gigenet.com/centos/ OK: rsync://mirrors.gigenet.com/centos/ OK: http://mirrors.serveraxis.net/centos/ OK: ftp://mirrors.serveraxis.net/centos/ OK: http://mirror.steadfast.net/centos/ OK: ftp://mirror.steadfast.net/centos/ OK: rsync://mirror.steadfast.net/centos/ OK: http://mirror.team-cymru.org/CentOS/ OK: ftp://mirror.team-cymru.org/CentOS/ OK: rsync://mirror.team-cymru.org/CentOS OK: http://centos.netnitco.net/ FAIL: ftp://centos.netnitco.net/centos/ OK: ftp://mirror.atlantic.net/pub/centos/ OK: http://ftp.belnet.be/packages/centos/ OK: ftp://ftp.belnet.be/packages/centos/ OK: rsync://ftp.belnet.be/packages/centos/ OK: http://be.mirror.eurid.eu/centos/ FAIL: ftp://be.mirror.eurid.eu/centos/ FAIL: rsync://centos.bg/mirror OK: http://ftp.fi.muni.cz/pub/linux/centos/ OK: ftp://ftp.fi.muni.cz/pub/linux/centos/ OK: rsync://ftp.fi.muni.cz/pub/linux/centos/ OK: http://mirror.hosting90.cz/centos/ FAIL: ftp://mirror.hosting90.cz/centos/ OK: http://mirror.karneval.cz/pub/centos/ OK: ftp://mirror.karneval.cz/pub/centos/ OK: http://centos.slu.cz/mirror/ FAIL: ftp://centos.slu.cz/centos/ FAIL: rsync://centos.slu.cz/CentOS FAIL: http://ftp.estpak.ee/pub/centos/ FAIL: ftp://ftp.estpak.ee/pub/centos/ FAIL: rsync://ftp.estpak.ee/centos OK: http://mirror.academica.fi/CentOS/ OK: ftp://mirror.academica.fi/CentOS/ FAIL: rsync://mirror.academica.fi/CentOS OK: http://ftp.funet.fi/pub/mirrors/centos.org/ OK: ftp://ftp.funet.fi/pub/mirrors/centos.org/ OK: rsync://rsync.nic.funet.fi/pub/mirrors/centos.org/ OK: http://ftp.ciril.fr/pub/linux/centos/ OK: ftp://ftp.ciril.fr/pub/linux/centos/ OK: rsync://ftp.ciril.fr/pub/linux/centos/ OK: ftp://ftp.free.fr/mirrors/ftp.centos.org/ OK: http://mirrors.ircam.fr/pub/CentOS/ OK: ftp://mirrors.ircam.fr/pub/CentOS/ OK: rsync://mirrors.ircam.fr/CentOS/ OK: http://mirror.ovh.net/ftp.centos.org/ OK: ftp://mirror.ovh.net/ftp.centos.org/ OK: rsync://mirror.ovh.net/ftp.centos.org/ FAIL: http://centos.crazyfrogs.org/ FAIL: rsync://centos.crazyfrogs.org/centos/ OK: http://mirror.checkdomain.de/centos OK: ftp://mirror.checkdomain.de/centos OK: http://ftp.hosteurope.de/mirror/centos.org/ OK: ftp://ftp.hosteurope.de/mirror/centos.org/ FAIL: rsync://ftp.hosteurope.de/centos/ OK: http://mirror.de.leaseweb.net/centos/ FAIL: ftp://mirror.de.leaseweb.net/centos/ OK: rsync://mirror.de.leaseweb.net/centos/ OK: http://centos.bio.lmu.de/ FAIL: ftp://centos.bio.lmu.de/centos/ FAIL: rsync://centos.bio.lmu.de/CentOS/ OK: http://mirror.netcologne.de/centos/ OK: ftp://mirror.netcologne.de/centos/ OK: rsync://mirror.netcologne.de/centos/ OK: http://centos.kiewel-online.ch/centos/ FAIL: ftp://mirror.kiewel-online.ch/centos/ OK: http://ftp.plusline.de/centos/ OK: ftp://ftp.plusline.de/pub/centos/ OK: rsync://ftp.plusline.de/CentOS/ OK: http://ftp.freepark.org/pub/linux/distributions/centos/ OK: ftp://ftp.freepark.org/pub/linux/distributions/centos/ OK: rsync://ftp.freepark.org/linux/centos/ OK: http://ftp.heanet.ie/pub/centos/ OK: ftp://ftp.heanet.ie/pub/centos/ OK: rsync://ftp.heanet.ie/pub/centos/ FAIL: ftp://ftp.eutelia.it/CentOS FAIL: ftp://ftp.eutelia.it/CentOS/ OK: http://mi.mirror.garr.it/mirrors/CentOS/ OK: ftp://mi.mirror.garr.it/mirrors/CentOS/ OK: rsync://mi.mirror.garr.it/CentOS/ OK: http://centos.linux.edu.lv/ OK: http://centos.mirror.root.lu/ OK: ftp://mirror.root.lu/centos/ OK: rsync://mirror.root.lu/CentOS OK: http://centos.ustc.edu.cn/centos/ OK: http://ftp.cuhk.edu.hk/pub/Linux/centos/ OK: ftp://ftp.cuhk.edu.hk/pub/Linux/centos/ OK: http://ftp.iij.ad.jp/pub/linux/centos/ OK: ftp://ftp.iij.ad.jp/pub/linux/centos/ FAIL: rsync://ftp.iij.ad.jp/centos/ OK: http://ftp.jaist.ac.jp/pub/Linux/CentOS/ OK: ftp://ftp.jaist.ac.jp/pub/Linux/CentOS/ OK: rsync://ftp.jaist.ac.jp/pub/Linux/CentOS/ OK: ftp://ftp.kddilabs.jp/Linux/packages/CentOS/ OK: rsync://rsync.kddilabs.jp/centos/ OK: http://ftp.nara.wide.ad.jp/pub/Linux/centos/ OK: ftp://ftp.nara.wide.ad.jp/pub/Linux/centos/ OK: rsync://ftp.nara.wide.ad.jp/centos OK: http://ftp.tsukuba.wide.ad.jp/Linux/centos/ OK: http://ftp.yz.yamagata-u.ac.jp/pub/linux/centos/ OK: ftp://ftp.yz.yamagata-u.ac.jp/pub/linux/centos/ FAIL: http://stingray.cyber.net.pk/pub/centos/ FAIL: ftp://stingray.cyber.net.pk/pub/centos/ FAIL: rsync://stingray.cyber.net.pk/pub/centos/ OK: http://mirror.learn.ac.lk/centos/ FAIL: ftp://mirror.learn.ac.lk/pub/centos/ OK: rsync://mirror.learn.ac.lk/centos/ OK: http://ftp.stu.edu.tw/Linux/CentOS/ OK: ftp://ftp.stu.edu.tw/Linux/CentOS/ OK: http://ftp.twaren.net/Linux/CentOS/ OK: ftp://ftp.twaren.net/Linux/CentOS/ OK: http://ftp.nsysu.edu.tw/CentOS/ FAIL: ftp://ftp.nsysu.edu.tw/CentOS/ OK: http://ftp.tc.edu.tw/Linux/CentOS/ FAIL: ftp://ftp.tc.edu.tw/Linux/Centos/ OK: http://mirror.aarnet.edu.au/pub/centos/ OK: ftp://mirror.aarnet.edu.au/pub/centos/ OK: rsync://mirror.aarnet.edu.au/centos/ OK: http://mirror.as24220.net/pub/centos/ OK: ftp://mirror.as24220.net/pub/centos/ OK: rsync://mirror.as24220.net/pub/centos/ OK: http://mirror.primusdatacentre.com.au/centos/ FAIL: ftp://mirror.primusdatacentre.com.au/centos/ OK: http://ftp.swin.edu.au/centos/ OK: ftp://ftp.swin.edu.au/centos/ OK: rsync://ftp.swin.edu.au/centos/ OK: http://centos.mirror.uber.com.au/ OK: rsync://mirror.uber.com.au/centos OK: http://mirrors.coopvgg.com.ar/centos/ OK: ftp://mirrors.coopvgg.com.ar/centos/ OK: rsync://mirrors.coopvgg.com.ar/centos/ FAIL: ftp://ftp.inf.utfsm.cl/pub/Linux/CentOS/ FAIL: rsync://ftp.inf.utfsm.cl/pub/Linux/CentOS/ OK: http://mirror.denit.net/centos/ FAIL: ftp://mirror.denit.net/centos/ OK: http://nl.mirror.eurid.eu/centos/ FAIL: ftp://nl.mirror.eurid.eu/centos/ OK: http://mirror.nl.leaseweb.net/centos/ FAIL: ftp://mirror.nl.leaseweb.net/centos/ OK: rsync://mirror.nl.leaseweb.net/centos/ OK: http://centos.mirror.serverbeheren.nl/ FAIL: rsync://centos.mirror.serverbeheren.nl/centos/ OK: http://ftp.nluug.nl/ftp/pub/os/Linux/distr/CentOS/ OK: ftp://ftp.nluug.nl/pub/os/Linux/distr/CentOS/ OK: rsync://ftp.nluug.nl/CentOS/ OK: http://mirror.oxilion.nl/centos/ OK: ftp://mirror.oxilion.nl/centos/ OK: rsync://mirror.oxilion.nl/centos/ OK: http://centos.uib.no/ OK: ftp://centos.uib.no/pub/Linux/Distributions/centos/ OK: rsync://centos.uib.no/centos/ OK: http://ftp.uninett.no/pub/Linux/centos/ OK: ftp://ftp.uninett.no/pub/linux/centos/ OK: rsync://ftp.uninett.no/centos/ FAIL: http://centos.hitme.net.pl/ OK: http://mirrors.nfsi.pt/CentOS/ OK: ftp://ftp.nfsi.pt/pub/CentOS/ OK: http://ftp.iasi.roedu.net/mirrors/centos.org/ OK: ftp://ftp.iasi.roedu.net/mirrors/centos.org/ OK: rsync://ftp.iasi.roedu.net/centos/ OK: http://ftp.ines.lug.ro/centos/ OK: ftp://ftp.ines.lug.ro/centos/ OK: http://mirror.corbina.net/pub/Linux/centos/ OK: ftp://mirror.corbina.net/pub/Linux/centos/ OK: rsync://mirror.corbina.net/centos OK: http://mirror.yandex.ru/centos/ OK: ftp://mirror.yandex.ru/centos/ OK: rsync://mirror.yandex.ru/centos/ OK: http://ftp.energotel.sk/pub/linux/centos/ OK: ftp://ftp.energotel.sk/pub/linux/centos/ OK: rsync://ftp.energotel.sk/centos/ OK: http://ftp.arnes.si/pub/mirrors/centos.org/ OK: ftp://ftp.arnes.si/mirrors/centos.org/ OK: http://mirror.lihnidos.org/CentOS/ OK: http://ftp.cica.es/CentOS/ OK: ftp://ftp.cica.es/CentOS/ FAIL: rsync://rsync.cica.es/CentOS/ OK: http://ftp.sunet.se/pub/Linux/distributions/centos/ OK: ftp://ftp.sunet.se/pub/Linux/distributions/centos/ OK: rsync://ftp.sunet.se/pub/Linux/distributions/centos/ OK: http://mirror.switch.ch/ftp/mirror/centos/ OK: ftp://mirror.switch.ch/mirror/centos/ OK: http://repo.boun.edu.tr/centos/ FAIL: ftp://repo.boun.edu.tr/centos/ OK: http://ftp.itu.edu.tr/Mirror/CentOS/ OK: ftp://ftp.itu.edu.tr/Mirror/CentOS/ FAIL: http://mirror.for.me.uk/centos/ OK: http://mirror.bytemark.co.uk/centos/ OK: ftp://mirror.bytemark.co.uk/centos/ OK: rsync://mirror.bytemark.co.uk/centos OK: http://mirrors.coreix.net/centos/ OK: http://mirror.sov.uk.goscomb.net/centos/ OK: ftp://mirror.sov.uk.goscomb.net/centos/ OK: http://centos.mirror.bradiceanu.net/ OK: ftp://centos.mirror.bradiceanu.net/centos/ OK: rsync://mirror.bradiceanu.net/CentOS FAIL: http://mirror.its.dal.ca/centos/ FAIL: ftp://mirror.its.dal.ca/centos/ FAIL: rsync://mirror.its.dal.ca/centos/ OK: http://centos.mirror.nexicom.net/ FAIL: ftp://mirror.nexicom.net/pub/centos/ OK: rsync://mirror.nexicom.net/CentOS OK: http://centos.mirror.iweb.ca/ OK: ftp://centos.mirror.iweb.ca/ OK: rsync://centos.mirror.iweb.ca/centos OK: http://mirror.metrocast.net/centos/ OK: http://mirror.atlanticmetro.net/centos/ FAIL: ftp://mirror.atlanticmetro.net/centos/ OK: http://mirrors.cat.pdx.edu/centos/ OK: rsync://mirrors.cat.pdx.edu/centos/ OK: http://centos.mirror.lstn.net/ FAIL: ftp://centos.mirror.lstn.net/ OK: rsync://centos.mirror.lstn.net/ OK: http://mirror.chpc.utah.edu/pub/centos/ OK: rsync://mirror.chpc.utah.edu/pub/centos/ OK: http://mirrors.xmission.com/centos/ OK: ftp://mirrors.xmission.com/centos/ OK: rsync://mirrors.xmission.com/centos/ OK: http://mirror.us.leaseweb.net/centos/ FAIL: ftp://mirror.us.leaseweb.net/centos/ OK: rsync://mirror.us.leaseweb.net/centos/ FAIL: http://centos.supsec.org/ FAIL: ftp://centos.supsec.org/pub/linux/centos/ FAIL: rsync://centos.supsec.org/centos/ OK: http://mirror.cs.vt.edu/pub/CentOS/ FAIL: ftp://mirror.cs.vt.edu/pub/CentOS/ FAIL: http://mirror.yellowfiber.net/centos/ OK: http://mirror.teljet.net/centos OK: ftp://ftp.ne.jp/Linux/packages/CentOS/
The ones marked FAIL are mirrors which have an AAAA record but are not reachable by IPv6. My tests were done primarily from AS 29422, with some spot checking from ASs 29169 and 16276.
If you have concerns/doubts about some specific server's test results, feel free to contact me off-list for more details and/or more tests.
On 05/01/2012 10:35 PM, Anssi Johansson wrote:
Hi fellow mirror admins.
I made a list of mirrors that have a published AAAA record, and checked if those mirrors are actually reachable by IPv6. Unfortunately it looks like there is a significant amount of mirrors that do have an AAAA record, but the actual services (http, ftp, rsync) are not available by IPv6.
The aim here is to try and create, static if needed, list of mirrors to be served for ipv6 requests. If anyone on there wants to opt out, let us know now.
- KB
On Tue, May 01, 2012 at 05:14:28PM -0500, Karanbir Singh wrote:
On 05/01/2012 10:35 PM, Anssi Johansson wrote:
Hi fellow mirror admins.
I made a list of mirrors that have a published AAAA record, and checked if those mirrors are actually reachable by IPv6. Unfortunately it looks like there is a significant amount of mirrors that do have an AAAA record, but the actual services (http, ftp, rsync) are not available by IPv6.
The aim here is to try and create, static if needed, list of mirrors to be served for ipv6 requests. If anyone on there wants to opt out, let us know now.
I think the aim would be to get the mirror admins to either a) provide IPv6 service if they publish an AAAA record; or b) delete the AAAA record if they don't provide IPv6 service. Announce that policy, give folks a week, then start dropping mirrors from the master list who can't abide. CentOS in particular has plenty of mirrors worldwide, far more than many projects, with plenty of competent sysadmins. Don't create more work for yourself to manage a (transient) list of mirrors that have functional IPv6.
The MirrorManager crawler would, through using urlgrabber, try to establish an IPv6 connection to a mirror with an AAAA record first. I don't know if it would fall back to try A records if IPv6 fails, but I presume not. Such failing AAAA records would then cause the crawler to mark the mirror as not up-to-date, and automatically drop them from the mirrorlist until such a time their AAAA record actually works. I say "probably" here only because Fedora's infrastructure where this runs for them doesn't have IPv6 connectivity yet, so I haven't tested it in production use.
Thanks, Matt
Hi Matt,
On 05/04/2012 11:17 PM, Matt Domsch wrote:
can't abide. CentOS in particular has plenty of mirrors worldwide, far more than many projects, with plenty of competent sysadmins. Don't create more work for yourself to manage a (transient) list of mirrors that have functional IPv6.
Right, not longer term - but this was more of a stop-gap arrangement to get something going while we wait for MM to come online, longer term we would not want to manage something like this manually anyway.
The MirrorManager crawler would, through using urlgrabber, try to establish an IPv6 connection to a mirror with an AAAA record first. I don't know if it would fall back to try A records if IPv6 fails, but I presume not. Such failing AAAA records would then cause the crawler to mark the mirror as not up-to-date, and automatically drop them from the mirrorlist until such a time their AAAA record actually works. I say "probably" here only because Fedora's infrastructure where this runs for them doesn't have IPv6 connectivity yet, so I haven't tested it in production use.
Does that then imply that machines which do have an AAAA will not be used / served for A records ? ( or tested for that matter )
On Sun, May 06, 2012 at 04:30:02PM -0500, Karanbir Singh wrote:
Does that then imply that machines which do have an AAAA will not be used / served for A records ? ( or tested for that matter )
There are 2 components:
1) URLs handed to end users. These are simply URLs, the client (yum, browser for download links, ...) does its own address resolution and decision as to which IPv[46] address to use.
2) The MM crawler. It does its own address resolution (via urlgrabber), and doesn't try both IPv4 and IPv6 if both types of records are available.
-
Anssi Johansson -
Karanbir Singh -
Matt Domsch