Mailinglist Archive: opensuse (1047 mails)

< Previous Next >
[opensuse] Re: Strange update problem - Leap 42.1
On Sun, 10 Jan 2016 14:11, Gustav Degreef wrote:
On 01/10/2016 09:41 AM, Per Jessen wrote:
Gustav Degreef wrote:
On 01/09/2016 05:15 PM, Per Jessen wrote:
Gustav Degreef wrote:
On 01/08/2016 03:32 PM, Per Jessen wrote:
Gustav Degreef wrote:
On 01/08/2016 02:54 PM, Per Jessen wrote:
Gustav Degreef wrote:

That looks fine - your machine is 1.33, your router is 1.1. It
sounds like "Network is unreachable" is caused by your "zypper
ref" trying to
use the IPv6 address of "download.opensuse.org". Do you still
get this error?

What does "host download.opensuse.org" say? On a systems with no
IPv6 connectivity, you ought to see the IPv4 address listed
first.

Thanks Per. The results now are:
user@linux:~> host download.opensuse.org
download.opensuse.org has address 195.135.221.134
download.opensuse.org has IPv6 address 2001:67c:2178:8::13
;; connection timed out; no servers could be reached
The last line is a little odd, not sure where that would be from.
Otherwise fine.

user@linux:~> ping6 download.opensuse.org
PING download.opensuse.org(ftp.opensuse.org) 56 data bytes
From fe80::1 icmp_seq=1 Destination unreachable: No route
Hmm, let us see your network config, please: "ip addr"
It is odd that you should have an IPv6 address (fe80::1) saying "no
route". Judging by your "ip addr" output, you only have link-local
addresses, but I wonder if you might have an IPv6 route, default
fe80::1. What does "ip -6 route show" say?

fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fe80::1 dev eth0 proto static metric 100 pref medium

Okay, there is your problem. When zypper tries to
access "download.opensuse.org", it will attempt to use IPv6, because
you appear to have IPv6 connectivity. When the first packet is routed
to fe80::1, it is returned with "Network is unreachable" because your
router doesn't actually have any IPv6 connectivity.
It's probably easily fixed by changing to dhcp4 only for your network
interfaces. This is done with YaST.

Thanks Per. I went to Yast > Network Config > General options. There I
unchecheked the enable Ipv6 and then as instructed by Yast rebooted. But it had NO
effect. Problem is unchanged. It's really puzzling. Gustav.


Shorted from above:
Wah!-Comp-wants-to-use-IPv6-but-I-have-only-IPv4-no-connect-at-all

Hmm, have you ever heard of "/etc/gai.conf" ? Nifty file to configure
just HOW that damn glibc orders the get-address-info stuff.

Esp. a line of:
[code]
precedence ::ffff:0:0/96 100
[/code]
helps in such troubles. Most times it is already there, but commented out.

May need a reboot, but most often not.

- Yamaban.
--
Live: Shit happens, then you die.
The trick is to make sure it's your shit that happens.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups