On 2011-06-09 16:06, Ansus wrote:
>
>>
>> That is not zypper fault. Zypper asks for the IP of a certain name and
>> is
>> given back an IPv6 address. There is no IPv4 address.
>>
> The both IPv4 and IPv6 addresses of that site were enabled that day.
> And zypper stubbornly tried to connect only via IPv6 enen though it was
> unavailable.
But your domain name server replies with the IPv6 address first (or only).
Zypper does what it has to do, what any other program does.
This is known. Not a bug, this is the expected behavior.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2011-06-09 16:06, Ansus wrote:
>
>>
>> Zypper does support it very well.
> Really? In that case why it did not connect via IPv4 once it determined
> that IPv6 is unavailable?
>
>> Your ISP or router does not.
>>
> What should it support? All other sites work well.
Your ISP is giving you an IPv6 address to contact, when your ISP does not
support IPv6. That is the problem.
Look, this has been known for ages. Users normally notice that FF goes very
slow, because it tries to download from IPv6 addresses first. The hack is
to disable IPv6 in the kernel. You can find many threads here, for several
years, with this solution.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2011-06-09 16:06, Ansus wrote:
>
> djh-novell;2351197 Wrote:
>>
>> Does it? It doesn’t match ansus statement.
>
> I really do not understand what they tested.
Things like this.
> There is no IPv6 in Russia, only in
There is no IPv6 anywhere.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Carlos E. R. wrote:
> Look, this has been known for ages. Users normally notice that FF goes very
> slow, because it tries to download from IPv6 addresses first. The hack is
> to disable IPv6 in the kernel. You can find many threads here, for several
> years, with this solution.
Is there a difference in that FF does eventually use the IPv4 address,
whilst zypper apparently does not?
I think this is a subject of the current IPv6 testing day. It was known that some browsers (i.e., Opera around version 10.0) do not connect via IPv4 if there is an available IPv6 address in DNS. Some browsers (i.e. OS X Safari) took too long fall back to IPv4, about a minute. But now all those browsers were fixed, I experienced no problems nor delays with neither Firefox, nor even old 10.11 Opera that day. And I connected to sites which for sure have both IPv6 and IPv4 DNS entries (Google, Yandex etc).
On 2011-06-09 17:00, Dave Howorth wrote:
> Carlos E. R. wrote:
>> Look, this has been known for ages. Users normally notice that FF goes very
>> slow, because it tries to download from IPv6 addresses first. The hack is
>> to disable IPv6 in the kernel. You can find many threads here, for several
>> years, with this solution.
>
> Is there a difference in that FF does eventually use the IPv4 address,
> whilst zypper apparently does not?
That could be.
Although it is not zypper who does the connecting, it is an external app,
curl I think. At some time it was aria2c, I think.
What I don’t understand is why zypper, if some mirror does not work, why
doesn’t it try another. It has a list of 20 or so.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)