[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes

Amos Jeffries 1547640 at bugs.launchpad.net
Fri Feb 26 19:28:06 UTC 2016


Andres,
 Because there is no way to distinguish between a local-only network and one using NAT without actually trying to connect to the IPs (which is exactly what Squid is doing - up to the limit of forward_max_tries). The problem is identical and far more widespread in IPv4. Disabling IPv4 whenever RFC1918 addresses were the only ones assigned would cut a huge number of networks connectivity.

It simply comes down to the fact that despite some mistaken opinions to
the contrary, IPv6 is mandatory for any network that wishes to
communicate with the www. IPv4-only networks (even just on the global
facing part) will face more and more inability to communicate as time
passes. We can juggle some numbers to workaround the pain for a while.
But in the end IPv6 is mandatory.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1547640

Title:
  proxy tries ipv6 and gets 503 when no ipv6 routes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions



More information about the Ubuntu-server-bugs mailing list