Carlos E. R. wrote:
On 2012-05-30 17:18, Per Jessen wrote:
Carlos E. R. wrote:
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).
Zypper should be cleverer, yes.
Since a week or two I have done a configuration change for curl, I have a /root/.curlrc file with a line "--ipv4" which should force curl to use ipv4 always, but I still do not know if it is honored.
You could try running a tcpdump to catch ipv6 on port 80. Just leave it for a few weeks and see if it catches anything. [snip]
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.
Sorry, what configuration problem? I lost you.
Well, I don't know of course, but because I don't have this issue ("works for me") and I don't have external IPv6 connectivity, I think the current setup is working fine, and any problem with it is more likely to be due to a local configuration problem.
If you mean like the one I mentioned above for curl, yes, I did that and I'm trying to confirm it works. But many programs do not have a switch to force ipv4 or ipv6.
Because they don't need it. An IPv6-aware application that is having a problem on a IPv4-only network _could_ have been badly written, but for widely used applications, that is unlikely to be the reason. More likely it is a local configuration issue. -- Per Jessen, Zürich (20.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org