http://bugzilla.suse.com/show_bug.cgi?id=975913
http://bugzilla.suse.com/show_bug.cgi?id=975913#c8
--- Comment #8 from Peter Simons
$ lftp lftp :~> debug 9 lftp :~> open http://releases.ubuntu.com/ ---- Resolving host address... ---- 2 addresses found: 2001:7b8:3:37::21:3, 91.189.88.148 ---- Connecting to releases.ubuntu.com (2001:7b8:3:37::21:3) port 80 **** Socket error (Connection timed out) - reconnecting ---- Closing HTTP connection ---- Connecting to releases.ubuntu.com (91.189.88.148) port 80 ---- Sending request... ---> HEAD / HTTP/1.1 ---> Host: releases.ubuntu.com ---> User-Agent: lftp/4.7.3 ---> Accept: */* ---> Connection: keep-alive ---> <--- HTTP/1.1 200 OK <--- Date: Sun, 11 Sep 2016 11:50:08 GMT <--- Server: Apache/2.2.22 (Ubuntu) <--- Vary: Accept-Encoding <--- Keep-Alive: timeout=5, max=100 <--- Connection: Keep-Alive <--- Content-Type: text/html;charset=UTF-8 <--- cd ok, cwd=/
That delay *is* unpleasant and misleading, no doubt, but I'm not sure what we can do about this phenomenon. Lftp's default configuration is to prefer IPv6 over v4 and we ship it with that particular setting. Other tools use the opposite policy. So I guess the best we could do is to deviate from the tool's default and to ship a system-wide config file that prefers IPv4 over v6. Personally, I feel a little uncomfortable about that, but it's certainy doable if other feel it's the best solution. Another option might be to have Yast adapt that setting in lftp's config file whenever the state of IPv6 support is enabled or disabled. Not sure how realistic it is to get that implemented. -- You are receiving this mail because: You are on the CC list for the bug.