*** This bug is a duplicate of bug 1308200 ***
https://bugs.launchpad.net/bugs/1308200
The solution is extremely complicated. It requires a short (300ms)
timeout when falling back from IPv6 to IPv4 and then waiting on _both_.
And then properly reporting errors, so it reports failures for the
correct IP addresses.
I basically had a working prototype in July, but I had to abandon it,
because it did not pass CI. I think its error reporting also was fairly
shaky.
Re 16.04, I don't think we'll see a fix there. The changes are fairly
complex, and it only affects a tiny minority of users (*), and there is
a much easier workaround to apply. Also, this not only affects APT if
your libc is configured to prefer IPv6 on a system without real IPv6
connectivity - some apps just try the first address (IPv6 then), they
will hard-fail quickly.
(*) If someone ever can explain to me what causes this, please do so.
This should not happen. If you have a globally routable IPv6 address and
just drop the IPv6 traffic somewhere down the route, your network is
broken IMO. Don't expect everyone to add workarounds for that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740114
Title:
apt's IPv4 fallback in case of a malfunctioning IPv6 connection works
horribly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1740114/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
