mirrorlist IPv6 problem

[KarMann]

When I try to get the mirrorlist over IPv4, no problem, I get a list. When I try it with IPv6, it returns empty, and my system defaults to IPv6, and yum doesn't have a -4 type switch, so this is a bit of a problem.

Code: Select all

$ wget -4 -O - 'http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=updates'
--2015-05-24 16:54:45--  http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=updates
Resolving mirrorlist.centos.org... 84.22.180.89, 88.150.173.218, 108.61.16.227
Connecting to mirrorlist.centos.org|84.22.180.89|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: “STDOUT”

    [<=>                                                       ] 0           --.-K/s
http://dist1.800hosting.com/centos/6.6/updates/x86_64/
http://centos.host-engine.com/6.6/updates/x86_64/
http://mirror.hmc.edu/centos/6.6/updates/x86_64/
http://mirror.pac-12.org/6.6/updates/x86_64/
http://linux.mirrors.es.net/centos/6.6/updates/x86_64/
http://centos.mia.host-engine.com/6.6/updates/x86_64/
http://mirrors.unifiedlayer.com/centos/6.6/updates/x86_64/
http://bay.uchicago.edu/centos/6.6/updates/x86_64/
http://mirrors.mit.edu/centos/6.6/updates/x86_64/
http://centos.mirror.nac.net/6.6/updates/x86_64/
    [ <=>                                                      ] 517         --.-K/s   in 0s

2015-05-24 16:54:45 (53.2 MB/s) - written to stdout [517]

$ wget -6 -O - 'http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=updates'
--2015-05-24 16:54:52--  http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=updates
Resolving mirrorlist.centos.org... 2a02:2498:1:3d:5054:ff:fed3:e91a
Connecting to mirrorlist.centos.org|2a02:2498:1:3d:5054:ff:fed3:e91a|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 0 [text/plain]
Saving to: “STDOUT”

    [ <=>                                                      ] 0           --.-K/s   in 0s

2015-05-24 16:54:52 (0.00 B/s) - written to stdout [0/0]

When I try it with a telnet to port 80, it behaves consistently with this:

Code: Select all

$ telnet 2a02:2498:1:3d:5054:ff:fed3:e91a 80
Trying 2a02:2498:1:3d:5054:ff:fed3:e91a...
Connected to 2a02:2498:1:3d:5054:ff:fed3:e91a.
Escape character is '^]'.
GET /?release=6&arch=x86_64&repo=updates HTTP/1.1
Host: mirrorlist.centos.org
Connection: close

HTTP/1.1 200 OK
Server: nginx/1.0.15
Date: Sun, 24 May 2015 16:58:35 GMT
Content-Type: text/plain
Connection: close
Content-Length: 0

Connection closed by foreign host.
Exit 1

But, when I did it over IPv4:

Code: Select all

$ telnet 88.150.173.218 80
Trying 88.150.173.218...
Connected to 88.150.173.218.
Escape character is '^]'.
GET /?release=6&arch=x86_64&repo=updates HTTP/1.1
Host: mirrorlist.centos.org
Connection: close

HTTP/1.1 200 OK
Date: Sun, 24 May 2015 17:02:46 GMT
Server: Apache/2.2.15 (CentOS)
Connection: close
Transfer-Encoding: chunked
Content-Type: text/plain; charset=ISO-8859-1

205
http://dist1.800hosting.com/centos/6.6/updates/x86_64/
http://centos.host-engine.com/6.6/updates/x86_64/
http://mirror.hmc.edu/centos/6.6/updates/x86_64/
http://mirror.pac-12.org/6.6/updates/x86_64/
http://linux.mirrors.es.net/centos/6.6/updates/x86_64/
http://centos.mia.host-engine.com/6.6/updates/x86_64/
http://mirrors.unifiedlayer.com/centos/6.6/updates/x86_64/
http://bay.uchicago.edu/centos/6.6/updates/x86_64/
http://mirrors.mit.edu/centos/6.6/updates/x86_64/
http://centos.mirror.nac.net/6.6/updates/x86_64/

0

Connection closed by foreign host.
Exit 1

I noticed that IPv4 shows as Apache, but IPv6 claims nginx, so it does look like something's not right here.

Also, I've now tried the telnet from my home machine (the others so far were from a rented remote host), and when I telnet to the IPv6 address from here, the connection just times out. Something certainly seems amiss here.

(This probably isn't CentOS 6-specific, then, but I don't see a place for infrastructure in particular, so this seemed best.)

[KarMann]

Found the bug tracker, and the bug. http://bugs.centos.org/view.php?id=8766

[TrevorH]

This should have been fixed in the last few minutes.