ping6 mirrorlist.centos.org returns "connect: the network is not
accessible", which confirm what you said.
If you right and curl is indeed broken, how a such thing happened???
Should I reinstall curl?
Thank you
Nicolas
Le Thu, 24 Oct 2013 10:12:11 +0200, Zdenek Pavlas <zpavlas@xxxxxxxxxx> a
écrit:
Indeed the "IP" on the search line is not correct.
If I add the 192, nothing changes. If I remove this line, it comes back
after I reboot. Even if I remove Networkmanager, it comes back...
Likely you've replied "192.168.11.218" to the host.domain prompt,
so your domain is assumed to be 168.11.218 and the hostname is 192.
However, this should not be a problem when resolving fully qualified
hostnames. The real problem is that curl defaults to using ipv6 address
of mirrorlist.centos.org, but ipv6 packets can't reach the destination.
Try "ping6 mirrorlist.centos.org", it probably won't work.
IMO this is a bug in curl.
1) The fact that host has an ipv6 address does not imply it's reachable.
Curl should not try to use ipv6 unless you explicitly ask for that.
2) The fallback to ipv4 is probably broken in curl.
DOCS: "curl will connect to a server with IPv6 when a host lookup
returns an IPv6 address and fall back to IPv4 if the connection fails."
It apparently does not..
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
