This happened to me about 5 years ago. I had a router which was IPV4 and so was the host. The PC was set up for IPV6. Each dns lookup would timeout on IPV6 and would then try IPV4. I had to turn off IPV6 Bob R On 01/25/2013 08:28 AM, Per Jessen wrote:
James Knott wrote:
Per Jessen wrote:
It's not a bottleneck as such, it's most probably probably time-outs due to your system thinking it is able to reach non-local IPv6 addresses. The question is why is that happening? IPv6 shouldn't even be attempted, if a route is not available. Agree. I can think of one reason only - no IPv4 connectivity either, but then disabling IPv6 wouldn't help.
Even if link local IPv6 is available, a router is supposed to advertise a route to the Internet. If there's no route, then IPv6 shouldn't be tried. While there might be a slight delay for the compute to determine there is no route, once an IPv4 TCP connection is set up, IPv6 shouldn't be considered. Why does this only affect some? I haven't experienced it, even though I didn't have IPv6 disabled before I started using it. Same here, and I don't understand why this only happens on some systems.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org