Hello,
i was testing mirror list from our local network (ping to mirror is 0.0x) and i have noticed that our network after:
yum clean all and yum update
uses not our mirror, why its happening and how it can be fixed?
Our mirror is
centos.vpsnet.lt/centos 185.34.52.2
Thank you Jonas
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 24/02/16 16:44, jonas wrote:
Hello,
i was testing mirror list from our local network (ping to mirror is 0.0x) and i have noticed that our network after:
yum clean all and yum update
uses not our mirror, why its happening and how it can be fixed?
Our mirror is
centos.vpsnet.lt/centos 185.34.52.2
Thank you Jonas _______________________________________________
curl -4 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&cc=l...' returns a list of validated mirrors in your country, and I see yours in that list . So then it's up to the yum client to pick up one mirror from that list (usually through the fastestmirror plugin).
The same curl request over ipv6 doesn't return any mirror from .lt, as it seems none of those mirrors have AAAA record though.
Can you confirm that from your location the following query works (without forcing the cc=) : curl -4 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os'
Cheers, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Hello,
i have tested from one subnet in our local AS network and got result
curl -4 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os' http://centos.vpsnet.lt/centos/7.2.1511/os/x86_64/ http://centos.mirror.serveriai.lt/7.2.1511/os/x86_64/ http://mirror.bacloud.com/centos/7.2.1511/os/x86_64/ http://mirror.duomenucentras.lt/centos/7.2.1511/os/x86_64/ http://mirror-pl.kielcetechnologypark.net/centos/7.2.1511/os/x86_64/ http://centos2.hti.pl/7.2.1511/os/x86_64/ http://ftp.prz.edu.pl/centos/7.2.1511/os/x86_64/ http://centos.slaskdatacenter.com/7.2.1511/os/x86_64/ http://centos.po.opole.pl/7.2.1511/os/x86_64/ http://mirror.onet.pl/pub/mirrors/centos/7.2.1511/os/x86_64/
everything looks fine
test 2 for ipv6
curl -6 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os' curl: (7) couldn't connect to host
ping6 mirrorlist.centos.org PING mirrorlist.centos.org(2a02:2498:1:3d:5054:ff:fed3:e91a) 56 data bytes ^C --- mirrorlist.centos.org ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 3998ms
ping6 ipv6.google.com PING ipv6.google.com(arn06s07-in-x0e.1e100.net) 56 data bytes 64 bytes from arn06s07-in-x0e.1e100.net: icmp_seq=1 ttl=56 time=13.9 ms ^C --- ipv6.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 13.958/13.958/13.958/0.000 ms
these test was made from 91.211.244.0/22 and if ipv6 from 2a05:7cc0::1/32
our ipv6 is working correctly:
ping6 2a05:7cc0::91:211:244:21 PING 2a05:7cc0::91:211:244:21(2a05:7cc0::91:211:244:21) 56 data bytes 64 bytes from 2a05:7cc0::91:211:244:21: icmp_seq=1 ttl=63 time=1.50 ms ^C --- 2a05:7cc0::91:211:244:21 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.501/1.501/1.501/0.000 ms
test from other subnet: 185.34.52.0/22
curl -4 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os' http://mirrors.supportex.net/centos/7.2.1511/os/x86_64/ http://mirror.sitbv.nl/centos/7.2.1511/os/x86_64/ http://mirrors.noction.com/centos/7.2.1511/os/x86_64/ http://mirror.oxilion.nl/centos/7.2.1511/os/x86_64/ http://mirror.nl.webzilla.com/centos/7.2.1511/os/x86_64/ http://mirror.netrouting.net/centos/7.2.1511/os/x86_64/ http://ftp.nluug.nl/ftp/pub/os/Linux/distr/CentOS/7.2.1511/os/x86_64/ http://mirror.1000mbps.com/centos/7.2.1511/os/x86_64/ http://ftp.tudelft.nl/centos.org/7.2.1511/os/x86_64/ http://mirror.widexs.nl/ftp/pub/os/Linux/distr/centos/7.2.1511/os/x86_64/
On 2/24/2016 6:04 PM, Fabian Arrotin wrote:
curl -4 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os
See inline comments
On 24/02/16 21:06, jonas wrote:
Hello,
i have tested from one subnet in our local AS network and got result
curl -4 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os' http://centos.vpsnet.lt/centos/7.2.1511/os/x86_64/ http://centos.mirror.serveriai.lt/7.2.1511/os/x86_64/ http://mirror.bacloud.com/centos/7.2.1511/os/x86_64/ http://mirror.duomenucentras.lt/centos/7.2.1511/os/x86_64/ http://mirror-pl.kielcetechnologypark.net/centos/7.2.1511/os/x86_64/ http://centos2.hti.pl/7.2.1511/os/x86_64/ http://ftp.prz.edu.pl/centos/7.2.1511/os/x86_64/ http://centos.slaskdatacenter.com/7.2.1511/os/x86_64/ http://centos.po.opole.pl/7.2.1511/os/x86_64/ http://mirror.onet.pl/pub/mirrors/centos/7.2.1511/os/x86_64/
everything looks fine
test 2 for ipv6
curl -6 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os' curl: (7) couldn't connect to host
Yes, we had a power outage in the rack hosting the VM responsible for ipv6 mirrorlist, but we restored the service so you can try again for ipv6.
ping6 mirrorlist.centos.org PING mirrorlist.centos.org(2a02:2498:1:3d:5054:ff:fed3:e91a) 56 data bytes ^C --- mirrorlist.centos.org ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 3998ms
ping6 ipv6.google.com PING ipv6.google.com(arn06s07-in-x0e.1e100.net) 56 data bytes 64 bytes from arn06s07-in-x0e.1e100.net: icmp_seq=1 ttl=56 time=13.9 ms ^C --- ipv6.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 13.958/13.958/13.958/0.000 ms
these test was made from 91.211.244.0/22 and if ipv6 from 2a05:7cc0::1/32
our ipv6 is working correctly:
ping6 2a05:7cc0::91:211:244:21 PING 2a05:7cc0::91:211:244:21(2a05:7cc0::91:211:244:21) 56 data bytes 64 bytes from 2a05:7cc0::91:211:244:21: icmp_seq=1 ttl=63 time=1.50 ms ^C --- 2a05:7cc0::91:211:244:21 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.501/1.501/1.501/0.000 ms
test from other subnet: 185.34.52.0/22
And that's where it "hurts" :
[arrfab@mirmon2 ~]$ curl http://ipinfo.io/185.34.52.2 { "ip": "185.34.52.2", "hostname": "backuppc.vpsnet.lt", "city": "", "region": "", "country": "NL", "loc": "52.3667,4.9000", "org": "AS61053 UAB Esnet" }
As you can see, the maxmind DB (and various services using it) think that this subnet is in .nl, reason why you have as answer from mirrorlist.centos.org a list of mirrors for that country. There is nothing we can do at our side (CentOS) so you'd rather see how to fix this with Maxmind.
curl -4 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os' http://mirrors.supportex.net/centos/7.2.1511/os/x86_64/ http://mirror.sitbv.nl/centos/7.2.1511/os/x86_64/ http://mirrors.noction.com/centos/7.2.1511/os/x86_64/ http://mirror.oxilion.nl/centos/7.2.1511/os/x86_64/ http://mirror.nl.webzilla.com/centos/7.2.1511/os/x86_64/ http://mirror.netrouting.net/centos/7.2.1511/os/x86_64/ http://ftp.nluug.nl/ftp/pub/os/Linux/distr/CentOS/7.2.1511/os/x86_64/ http://mirror.1000mbps.com/centos/7.2.1511/os/x86_64/ http://ftp.tudelft.nl/centos.org/7.2.1511/os/x86_64/ http://mirror.widexs.nl/ftp/pub/os/Linux/distr/centos/7.2.1511/os/x86_64/
On 2/24/2016 6:04 PM, Fabian Arrotin wrote:
curl -4 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os
-
Fabian Arrotin -
jonas