On 24/01/13 16:23, Bob Williams wrote:
On 24/01/13 14:59, James Knott wrote:
Dave Howorth wrote:
I'm curious as to why some people have problems with IPv6 turned on. Because some ISPs have their equipment incorrectly configured.
If they only provide IPv4, why is that an issue? If there's no IPv6 route out of a computer or local network, then it shouldn't affect IPv4. Does BW have IPv6 available? Every computer with a modern OS should have, at least, link local IPv6. In fact, Windows 7 uses it exclusively for the "Home Group" peer to peer networking. A computer shouldn't try to use IPv6 unless it's available for reaching the destination and the DNS returns AAAA records. Even then, once a TCP connection is established, IPv6 should not even be a factor.
James,
I acknowledge your expertise in this area, about which I know next to nothing. However, I can report that with IPv6 enabled it takes Yast > Software Management several minutes to download and rebuild the repo caches. With IPv6 disabled, the same process takes a few seconds.
I don't know where the bottleneck lies, YaST's configuration?, the openSUSE repository servers?, the aether?
Bob
I've been fighting this since I installed 12.2 on some machines, in fact I decided to delay switching from my faithful 11.4 until updates stopped. I found that it seemed OK on my main machine with dnsmasq but all others hardware or virtual were unusable with zypper because the dns failed if there was a long file downloaded. This happened if they used my main box for dns or my router/modem. It was only when I tried on another ISP system that the message changed and gave me an error message including an IPv6 address. I rebooted with IPv6 disabled and no errors or delays. Now with IPv6 disabled on all machines updates fly. My ISP will not be changing to IPv6 until latter in the year. Hope this helps someone. DC -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org