Hey folks,
the ISO Downloads from
http://isoredirect.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1708....
list several mirrors; but I have never seen mine there even tho I am synced and listed. Also the file is present:
http://centos.alpha-labs.net/7/isos/x86_64/CentOS-7-x86_64-DVD-1708.iso
Am I excluded on purpose there or do I have a missconfiguration that hides from me?
Cheers, -Christian
On Wed, 2017-12-20 at 16:05 +0100, Christian Reiß wrote:
Hey folks,
the ISO Downloads from
http://isoredirect.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-DV D-1708.iso
list several mirrors; but I have never seen mine there even tho I am synced and listed. Also the file is present:
http://centos.alpha-labs.net/7/isos/x86_64/CentOS-7-x86_64-DVD-1708.i so
Am I excluded on purpose there or do I have a missconfiguration that hides from me?
Cheers, -Christian
Hello,
Just checked our mirror to verify is it affected and found that one network of our ISP is actually affected. Below is how our networks are detected by isoredirect:
94.158.48.0/20 - Russian Federation 91.196.76.0/22 - Uzbekistan 185.196.216.0/22 - Uzbekistan
All networks actually deployed in Uzbekistan. RIPE database confirms it:
$ for IP in 94.158.48.1 91.196.76.1 185.196.216.1; do whois $IP; done | egrep 'country|inetnum' inetnum: 94.158.48.0 - 94.158.63.255 country: UZ inetnum: 91.196.76.0 - 91.196.79.255 country: UZ inetnum: 185.196.216.0 - 185.196.217.255 country: UZ
Thanks.
Garri Djavadyan kirjoitti 21.12.2017 klo 7.10:
Just checked our mirror to verify is it affected and found that one network of our ISP is actually affected. Below is how our networks are detected by isoredirect:
94.158.48.0/20 - Russian Federation 91.196.76.0/22 - Uzbekistan 185.196.216.0/22 - Uzbekistan
All networks actually deployed in Uzbekistan. RIPE database confirms it:
We do not maintain our own GeoIP database, but instead use MaxMind's free GeoIP database. The information regarding 94.158.48.0/20 seems to have changed recently. https://www.maxmind.com/en/geoip-demo shows Uzbekistan, but the CSV files at http://dev.maxmind.com/geoip/geoip2/geolite2/ that get updated monthly show Russia. It's likely that this isoredirect issue will disappear in about a month.
As for Christian's issue, the most likely reason why his mirror is not listed is that his mirror seems to be unreachable over IPv4 from our mirror crawler.
On Thu, 2017-12-21 at 08:21 +0200, Anssi Johansson wrote:
Garri Djavadyan kirjoitti 21.12.2017 klo 7.10:
Just checked our mirror to verify is it affected and found that one network of our ISP is actually affected. Below is how our networks are detected by isoredirect:
94.158.48.0/20 - Russian Federation 91.196.76.0/22 - Uzbekistan 185.196.216.0/22 - Uzbekistan
All networks actually deployed in Uzbekistan. RIPE database confirms it:
We do not maintain our own GeoIP database, but instead use MaxMind's free GeoIP database. The information regarding 94.158.48.0/20 seems to have changed recently. https://www.maxmind.com/en/geoip-demo shows Uzbekistan, but the CSV files at http://dev.maxmind.com/geoip/geoip2/geolite2/ that get updated monthly show Russia. It's likely that this isoredirect issue will disappear in about a month.
Anssi, thank you for the clue!
I found discrepancies in MaxMind's GeoIP DB and have sent corrections request.
On 20/12/17 16:05, Christian Reiß wrote:
Hey folks,
the ISO Downloads from
http://isoredirect.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1708....
list several mirrors; but I have never seen mine there even tho I am synced and listed. Also the file is present:
http://centos.alpha-labs.net/7/isos/x86_64/CentOS-7-x86_64-DVD-1708.iso
Am I excluded on purpose there or do I have a missconfiguration that hides from me?
Cheers, -Christian
I just checked the logs and it's because your mirror isn't available over ipv4 from the mirror crawler node :
<log> Name - alpha-labs.net - using url http://centos.alpha-labs.net/7/isos/x86_64/ alpha-labs.net going in timeout mirrors </log>
So I confirm that I can't reach it either with icmp (but you could be blocking it) or tcp/80 :
ping -c 4 centos.alpha-labs.net PING platform.alpha-labs.net (84.246.124.43) 56(84) bytes of data.
--- platform.alpha-labs.net ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 12999ms
/dev/tcp/84.246.124.43/80
-bash: connect: Connection timed out -bash: /dev/tcp/84.246.124.43/80: Connection timed out
I then tested routing issue and I confirm that with mtr (last two hops) :
9. ae1-irt1.dus03.de.as13237.ne 0.0% 1 15.5 15.5 15.5 15.5 0.0 10. 217.71.101.42 0.0% 1 12.2 12.2 12.2 12.2 0.0 11. ??? 100.0 1 0.0 0.0 0.0 0.0 0.0
So a routing issue somewhere. Maybe contact your ISP ?
-
Anssi Johansson -
Christian Reiß -
Fabian Arrotin -
Garri Djavadyan