Zypper can’t connect to download.opensuse.org:
$ sudo zypper ref
Download (curl) error for 'http://download.opensuse.org/repositories/LibreOffice:/Stable/openSUSE_12.2/repodata/repomd.xml':
Error code: Connection failed
Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable
However, ping works:
$ ping download.opensuse.org
PING download.opensuse.org (195.135.221.134) 56(84) bytes of data.
64 bytes from ftp.opensuse.org (195.135.221.134): icmp_seq=1 ttl=44 time=299 ms
64 bytes from ftp.opensuse.org (195.135.221.134): icmp_seq=2 ttl=46 time=292 ms
^C
--- download.opensuse.org ping statistics ---
3 packets transmitted, 2 received, 33% packet loss, time 2000ms
rtt min/avg/max/mdev = 292.592/296.077/299.563/3.527 ms
Firefox can’t load download.opensuse.org and times out.
Anybody facing same/similar problem?
I’m at work on a Windows machine with out access to my openSUSE machines, but download.opensuse.org loads fine in IE. Check your zypper logs in /var
On Fri, 09 Nov 2012 17:46:02 +0000, noisyboy wrote:
> Anybody facing same/similar problem?
Your zypper command is trying ipv6, but your ping command is using ipv4.
Suggest disabling ipv6 on the box and try again.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On 2012-11-09 22:36, Jim Henderson wrote:
> On Fri, 09 Nov 2012 17:46:02 +0000, noisyboy wrote:
>
>> Anybody facing same/similar problem?
>
> Your zypper command is trying ipv6, but your ping command is using ipv4.
> Suggest disabling ipv6 on the box and try again.
That may be a red herring. Often zypper fails with the ipv4 address, it
switches to other addresses in the list, likely the IPv6 address, which
fails for a different reason, and only then it reports the failure, but
only the last one. Result: you get a misleading error message.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
On Sat, 10 Nov 2012 01:24:12 +0000, Carlos E. R. wrote:
> On 2012-11-09 22:36, Jim Henderson wrote:
>> On Fri, 09 Nov 2012 17:46:02 +0000, noisyboy wrote:
>>
>>> Anybody facing same/similar problem?
>>
>> Your zypper command is trying ipv6, but your ping command is using
>> ipv4.
>> Suggest disabling ipv6 on the box and try again.
>
> That may be a red herring. Often zypper fails with the ipv4 address, it
> switches to other addresses in the list, likely the IPv6 address, which
> fails for a different reason, and only then it reports the failure, but
> only the last one. Result: you get a misleading error message.
It may not be the reason, but it’s certainly worth eliminating as a
possible problem.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On 2012-11-10 06:22, Jim Henderson wrote:
> It may not be the reason, but it’s certainly worth eliminating as a
> possible problem.
Unfortunately (for me and others) I do want IPv6 locally and not across
internet.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
On Sat, 10 Nov 2012 13:04:12 +0000, Carlos E. R. wrote:
> On 2012-11-10 06:22, Jim Henderson wrote:
>> It may not be the reason, but it’s certainly worth eliminating as a
>> possible problem.
>
> Unfortunately (for me and others) I do want IPv6 locally and not across
> internet.
That’s fine, it’s still a valid troubleshooting step. That’s how
troubleshooting is done - eliminate variables until you find what’s wrong.
Then once you’ve figured out what’s wrong, you can work to resolve it in
a way that meets your needs (such as local ipv6 and non-local ipv4).
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Sat, 10 Nov 2012 21:39:52 +0000, Jim Henderson wrote:
> On Sat, 10 Nov 2012 13:04:12 +0000, Carlos E. R. wrote:
>
>> On 2012-11-10 06:22, Jim Henderson wrote:
>>> It may not be the reason, but it’s certainly worth eliminating as a
>>> possible problem.
>>
>> Unfortunately (for me and others) I do want IPv6 locally and not across
>> internet.
>
> That’s fine, it’s still a valid troubleshooting step. That’s how
> troubleshooting is done - eliminate variables until you find what’s
> wrong.
>
> Then once you’ve figured out what’s wrong, you can work to resolve it in
> a way that meets your needs (such as local ipv6 and non-local ipv4).
This discussion reminds me in a lot of ways of talking with entry-level
CS students who don’t understand that they can, in their code, add debug
statements to print out variables at various points in their program to
see what’s going wrong. You don’t leave that debug code in when you turn
the assignment in, but one shouldn’t limit ones self to only the desired
end result when problem solving.
Too many times when I was at uni did I have to advise students in the lab
working on assignments that it was perfectly OK to add in code that let
them see what was going on in their program, even if it wasn’t part of
the end result.
The same principle applies here, and there’s really no need to debate
it. 
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On 2012-11-10 22:42, Jim Henderson wrote:
>>> Unfortunately (for me and others) I do want IPv6 locally and not across
>>> internet.
>>
>> That’s fine, it’s still a valid troubleshooting step. That’s how
>> troubleshooting is done - eliminate variables until you find what’s
>> wrong.
>>
>> Then once you’ve figured out what’s wrong, you can work to resolve it in
>> a way that meets your needs (such as local ipv6 and non-local ipv4).
Unfortunately, I haven’t been successful in that goal. My aim was to get
the name system to delete all IPv6 answers, or something similar, so
that programs do not attempt to connect to IPv6 servers out there (I
asked about that). No way.
The only solution is to block the stack IPv6 entirely 
> This discussion reminds me in a lot of ways of talking with entry-level
> CS students who don’t understand that they can, in their code, add debug
> statements to print out variables at various points in their program to
> see what’s going wrong. You don’t leave that debug code in when you turn
> the assignment in, but one shouldn’t limit ones self to only the desired
> end result when problem solving.
Well, I was told that trick very early in several courses, I think.
Starting with BASIC. Either they told me or I found out, I don’t remember.
Later I did them with an IFDEF clause or equivalent, no need to delete them.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
On Sun, 11 Nov 2012 03:34:11 +0000, Carlos E. R. wrote:
> Unfortunately, I haven’t been successful in that goal. My aim was to get
> the name system to delete all IPv6 answers, or something similar, so
> that programs do not attempt to connect to IPv6 servers out there (I
> asked about that). No way.
>
> The only solution is to block the stack IPv6 entirely
Which means my suggestion of disabling IPv6 is certainly a valid one to
test, so I’m not sure why we’re arguing about that.
>> This discussion reminds me in a lot of ways of talking with entry-level
>> CS students who don’t understand that they can, in their code, add
>> debug statements to print out variables at various points in their
>> program to see what’s going wrong. You don’t leave that debug code in
>> when you turn the assignment in, but one shouldn’t limit ones self to
>> only the desired end result when problem solving.
>
> Well, I was told that trick very early in several courses, I think.
> Starting with BASIC. Either they told me or I found out, I don’t
> remember.
>
> Later I did them with an IFDEF clause or equivalent, no need to delete
> them.
Sure, but that misses my point - in my decades of experience, most people
(especially those without a technical background, but even many with one)
don’t think about anything other than their end goal, and if a
troubleshooting step isn’t something they’d leave in place for their
“final solution”, they don’t even consider it a valid troubleshooting
step.
That’s poor troubleshooting, and poor logic.
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C