Adam Sailer wrote:

...

I can't update via Yast or Zypper, as each are attempting to refresh the software repositories via IPv6 addresses.

Currently using 12.1, 64-bit. I'm NOT on an IPv6 capable network.

Is there an easy way to resolve this issue?

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.

-- Per Jessen, Zürich (9.6°C)

How would I check for, and if need be, add a missing default IPv4 route?

"route -n" will tell you. Otherwise just ping a known external ipv4 address, e.g. download.opensuse.org. Anyway, as Marcus reported, it was a server problem. -- Per Jessen, Zürich (15.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

James Knott wrote:

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.

The vast majority of apps don't know anything about IPv6 or IPv4. That's determined by the IP stack.

Probably, but the scenario above still applies. -- Per Jessen, Zürich (24.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Apr 25, 2012 at 11:24:28PM -0700, Adam Sailer wrote:

...

Hello,

I can't update via Yast or Zypper, as each are attempting to refresh the software repositories via IPv6 addresses.

Currently using 12.1, 64-bit. I'm NOT on an IPv6 capable network.

Is there an easy way to resolve this issue?

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.

Hi, the host download.opensuse.org is effectively down currently. That the IPv6 address is shown is basically a misfeatuer, please read it as "download.opensuse.org unreachable: Connection timed out." Our admins are working on bringing up the host again. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-26 13:44, James Knott wrote:

How do you know it's trying IPv6? Normally, IPv6 is used only if available, otherwise IPv4.

Because the IP is listed in the failure message. I have seen it occasionally in yast. My router doesn't allow ipv6, nevertheless yast and zypper tries, fails, and aborts. If you tell it to retry, it tries the same IPv6 server instead of another. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+ZOjsACgkQIvFNjefEBxolIACgsfdbTzrs7UQHkUqzO+MHckuF CAkAn1D8GHmaQQ4acB6AhEGIsZN59Gym =3Mi9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-26 15:06, Per Jessen wrote:

Carlos E. R. wrote:

download.opensuse.org has both ipv4 and ipv6 addresses. If ipv4 doesn't work (for whatever reason), zypper will try ipv6 and report that failure (if it fails).

I Think I got confused with another failure mode: that in which we get redirected to a mirror that has IPv6 or only IPv6 (I'm not clear on this). The download thus fails and we get a message with the IP of the mirror, and the typical abort, ignore, retry question. There is either a problem with the redirector giving an IP we can not use, or the system that on retry doesn't try a different mirror, but the same mirror that failed. That is the failure I have experienced, and is different from the failure reported today in this thread. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+ZSr4ACgkQIvFNjefEBxr5xgCfeB+72kvXlWef0ZlUiuOYl/UH NUMAnRdY3UDrCctdZK5e3KDgYO2MQYdW =B098 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Rodney Baker [04-26-12 08:27]:

If you are not on an IPv6 capable network there is no need to have IPv6 enabled at all. You can turn it of by going to Yast2 -> Network Devices -> Network Settings -> Global Options -> uncheck "Enable IPv6" under IPv6 Protocol Settings. You will need to reboot for this setting to take effect.

hickup: I do not have IPv6 but do have it enabled as w/o I do not have ssh access to those machines :^( Began w/11.2 -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-26 15:14, Rodney Baker wrote:

Either way, that sounds like a misconfiguration of sshd. I have IPv6 turned off on mine and I can access it via ssh both from within the local lan and from outside using NAT and/or port forwarding.

The problem is that the case where there is IPv6 in the local network, but not in the internet access, is not handled nicely. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+ZS+QACgkQIvFNjefEBxrhjQCgrrVKu3iXwtFl/vdr7uTYUdwy nXYAoJHA5uosSEKSNjJKZ5Kx2dBHO9iN =Och6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-26 16:05, James Knott wrote:

Carlos E. R. wrote:

...

The problem is that the case where there is IPv6 in the local network, but not in the internet access, is not handled nicely.

There is always IPv6 in the local network, unless you turn it off. Every IPv6 capable device should have an IPv6 link local address, which started with "FE80". However the IP stack should see there's no route off the local network. Also, I've never turned off IPv6 and even when it wasn't available, I never had problems. I've had IPv6 for about 2 years, so it's enabled and works well.

That is my case, IPv6 is not disabled, but only works locally. The problem, as I said, is with zypper or yast, when they get a mirror with only an IPv6 address: the update halts. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk+ZjWQACgkQIvFNjefEBxrvVQCfcXC/Fwd/yBR414zACo2H4eJr 8mAAoMDWFifDCF8G5+9p4FW6khiyx6tq =ve5q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, 2012-04-27 at 01:09 +0200, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2012-04-26 20:01, Carlos E. R. wrote:

...

On 2012-04-26 16:05, James Knott wrote:

...

That is my case, IPv6 is not disabled, but only works locally. The problem, as I said, is with zypper or yast, when they get a mirror with only an IPv6 address: the update halts.

I got this right now:

Download (curl) error for 'http://download.opensuse.org/update/11.4/rpm/x86_64/wireshark-1.4.12-0.10.1....': Error code: Connection failed Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable

So, it seems to think it can reach the net via V6... what is your result of netstat -A inet6 -rn and ip -6 addr show As long as you only have lines with inet6 fe80::211:25ff:feb4:5f6b/64 scope link or like that, it should not be a problem, but if you get: inet6 2001:....scope global dynamic Your box will interprete the "scope global" as an invitation to use IPv6 hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, 2012-04-27 at 01:59 +0200, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2012-04-27 01:35, Hans Witvliet wrote:

...

So, it seems to think it can reach the net via V6...

what is your result of

netstat -A inet6 -rn and ip -6 addr show

Password:

...

Telcontar:~ # netstat -A inet6 -rn Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: U 256 0 0 vmnet1 fe80::/64 :: U 256 0 0 vmnet8 ::1/128 :: U 0 227175 1 lo fe80::221:85ff:fe16:2d0b/128 :: U 0 0 1 lo fe80::250:56ff:fec0:1/128 :: U 0 0 1 lo fe80::250:56ff:fec0:8/128 :: U 0 0 1 lo ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 vmnet1 ff00::/8 :: U 256 0 0 vmnet8 Telcontar:~ # ip -6 addr show 1: lo: mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qlen 1000 inet6 fe80::221:85ff:fe16:2d0b/64 scope link valid_lft forever preferred_lft forever 6: vmnet1: mtu 1500 qlen 1000 inet6 fe80::250:56ff:fec0:1/64 scope link valid_lft forever preferred_lft forever 7: vmnet8: mtu 1500 qlen 1000 inet6 fe80::250:56ff:fec0:8/64 scope link valid_lft forever preferred_lft forever Telcontar:~ #

...

As long as you only have lines with inet6 fe80::211:25ff:feb4:5f6b/64 scope link or like that, it should not be a problem, but if you get: inet6 2001:....scope global dynamic

Your box will interprete the "scope global" as an invitation to use IPv6

I don't have that... So, what do you think? I know next to nothing about v6.

That is indeed strange.. Normally, (i mean if you have v6 up-and-running) you see from netstat -A inet6 -rn a line with "::/0" indicating your default gateway for V6 (which often is different from you v4-gateway) Sometimes that can be rather misleading: on this laptop i see: ::/0 fe80::a00:20ff:feda:3b4a UGDA 1024 1214 0 eth5 That looks strange, as the "fe80::something" is a link local adres, but the ethernet device (eth5 in this case) has both a link-local AND a global adres: ip -6 addr show dev eth5 2: eth5: mtu 1500 qlen 1000 inet6 2001:...5f6b/64 scope global dynamic inet6 fe80:...5f6b/64 scope link On my firewall "netstat -A inet6 -rn" gives me: ::/0 U 1024 0 0 tun_82 Which indicates that all (non-local) v6 packets should go to my tunnel-provider. But in your case: you have neither a gateway for v6 defined, and only link-specific address.. So you _should_ be safe, but obviously you are not ;-( Weird indeed...... Could be an "undocumented feature" So the only short-term solution would be to get your updates from gwdg that gives you only an IPv4 addres, while the main-suse-site, and probably some mirrors, resolves to both v4 and v6. Only draw-back of gwdg, is that it seems to be limited to 20Mbps Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Rodney Baker [04-26-12 09:16]:

...

I do not have IPv6 but do have it enabled as w/o I do not have ssh access to those machines :^( Began w/11.2

I'm not sure I understand - without it enabled you can't access the machines (with IPv6 enabled) remotely via ssh, or you can't use ssh from that/those machine/s to connect out to others?

cannot access those machines w/IPv6 disabled.

Either way, that sounds like a misconfiguration of sshd. I have IPv6 turned off on mine and I can access it via ssh both from within the local lan and from outside using NAT and/or port forwarding.

access is lost from local and remote(NAT). I have not tried port forwarding for ssh ..... I found I had a problem w/ssh and someone else with the same experience happen to post their findings re IPv6. I can probably cite the post if you wish. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org