On Wed, 2012-04-25 at 23:24 -0700, Adam Sailer wrote:
When I had the same issue just recently, it was due to a missing default IPv4 route. I assume zypper tries ipv4 first, fails, then tries ipv6, fails, then reports the latter as the problem.
Eventhough the problem lies somewhere else (host down) and has been resolved, i wonder if your assumption is correct. Most deamons use a more progressive approach: First they try IPv6 and when no global route available, try IPv4. I had the sort like issue some time ago: My v6-in-v4 tunnel was down, but all of my nodes still had an V6 address and v6 routing was still there, so it (ssh, http, etc) assumed it could use v6. Googling was funny: it came with results but some hosts had to be clicked twice, as the first one yielded "host un reachable". With regard to updating, you could force your system to use ipv4-only ftp5.gwdg.de/pub/opensuse/ (ftp, http or rsync) I understood that they had quite some bandwith towards the university network... hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org