-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/07/15 15:20, Dominik Nowacki wrote:
Hi,
Our Customers get US mirrors while using our IPv6 subnets (range 2a04:92c0::/29) and UK mirrors while using our IPv4 subnets (range 185.42.223.0/24), while all subnets are used, and marked as GB.
As a result of that IPv6 enabled host have very slow download speeds and use international connectivity while they could use local mirrors.
curl -4 --silent 'http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=updates&...'
http://mirror.bytemark.co.uk/centos/6.6/updates/x86_64/
http://mirror.simwood.com/centos/6.6/updates/x86_64/
http://www.mirrorservice.org/sites/mirror.centos.org/6.6/updates/x86_64/
http://mirror.vorboss.net/centos/6.6/updates/x86_64/
http://mirrors.vooservers.com/centos/6.6/updates/x86_64/
http://centos.muzzy.org.uk/6.6/updates/x86_64/
http://mirror.econdc.com/centos/6.6/updates/x86_64/
http://mirrors.ukfast.co.uk/sites/ftp.centos.org/6.6/updates/x86_64/
http://mirror.ox.ac.uk/sites/mirror.centos.org/6.6/updates/x86_64/
http://mirror.synergyworks.co.uk/centos/6.6/updates/x86_64/
curl -6 --silent 'http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=updates&...'
http://mirrors.centarra.com/centos/6/updates/x86_64/
http://centos.den.host-engine.com/6/updates/x86_64/
http://mirror.vtti.vt.edu/centos/6/updates/x86_64/
http://mirrors.cat.pdx.edu/centos/6/updates/x86_64/
http://mirrors.kernel.org/centos/6/updates/x86_64/
http://centos.chi.host-engine.com/6/updates/x86_64/
http://mirror.metrocast.net/centos/6/updates/x86_64/
http://lug.mtu.edu/centos/6/updates/x86_64/
http://mirror.yellowfiber.net/centos/6/updates/x86_64/
http://repos.lax.quadranet.com/centos/6/updates/x86_64/
How to fix that ? I suppose that’s something to do with geo IP database, can you fix on your end or shall we contact someone (which geo IP DB are you using in that case?) ?
Thanks!
With Kind Regards,
Dominik Nowacki
Hi,
Yes, it seems there is an issue wrt ipv6 mirrorlist node, and I already asked to KB (managing that node) to have a look at that .. I'd guess it's a problem with the maxmind GeoIP DB not being up2date on that node (as it works fine on the ipv4 mirrorlists nodes)
Such report would be good to have on bugs.centos.org though, so that it can also be tracked
Cheers,
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab