Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-05-30 15:44, Per Jessen wrote:
Carlos E. R. wrote:
Well, the problem is that some applications try to connect via IPv6 instead of trying another server that has an IPv4 address. One such is zypper/yast.
That sounds like like a bug then - when your system has no route to the IPv6 address, any attempts from zypper should fail immediately, and the next mirror can be tried.
And they fail (I don't know the timing for this, inmediate of after time out), but a second mirror is not tried. It asks the user what to do.
That is either a zypper or libcurl problem, I would say. Unless of course it's failing for download.opensuse.org in which case there may not be another mirror. (for the metalink file for instance).
A neat solution would be that none of those applications knew that there existed IPv6 addresses, and so could not try them.
Yes that would cure the symptom, but it would be better to investigate the cause, i.e. why those applications don't work like e.g. ping6 (from my earlier posting).
I don't know if they fail intermediately, I think it does. Lets try, forcing ipv6:
cer@Telcontar:~> curl -o p --ipv6 http://download.opensuse.org/distribution/11.4/repo/oss/INDEX.gz
curl: (7) Failed to connect to 2001:67c:2178:8::13: Network is unreachable cer@Telcontar:~>
It fails instantly, that's good. The problem, for some people, is that sometimes it tries to use IPv6.
Because it "works for me" (I currently only have link-local IPv6), I would tend to say that is a configuration problem, and those people ought to pursue that first. -- Per Jessen, Zürich (26.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org