Bug#684407: apt: connection to Debian mirror with both A and AAAA records fails if client has no routable IPv6 address
On 2017-07-19 14:03:01 +0200, Julian Andres Klode wrote:
> I can't reproduce this, but you just marked it as found in 1.5~beta1. All
> my networks are IPv4-only (either just gw -> internet or entirely) and I
> never had any issue with that, nor does the majority - otherwise we'd
> be swimming in bug mails, so it must be some niche setup.
I suspect that most users have a working IPv6 address or no global
IPv6 address at all. Actually, that's the normal set-up. What happens
here is either IPv6 is partly down or there's a SLAAC attack.
> I suggest you take a look at methods/connect.cc and see if you can
> come up with a fix. The code specifically iterates over all results
> it gets from getaddrinfo(). Alternatively, try to figure out when this
> bug happens.
Indeed, it finally manages to connect, but it appears that there
is something like up to an 8-minute timeout. This is too much!
Here I got:
Fetched 88.4 kB in 8min 0s (183 B/s)
This should be shortened, or an option should be added.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: