On Thu, Feb 3, 2011 at 1:21 PM, George Herbert george.herbert@gmail.com wrote:
On Thu, Feb 3, 2011 at 1:11 PM, Jay Ashworth jra@baylink.com wrote:
----- Original Message -----
From: "River Tarnell" r.tarnell@IEEE.ORG
It doesn't matter if Apache supports IPv6, since the Internet-facing HTTP servers for wikis are reverse proxies, either Squid or Varnish. I believe the version of Squid that WMF is using doesn't support IPv6.
Oh, of course.
As long as the proxy supports IPv6, it can continue to talk to Apache via IPv4; since WMF's internal network uses RFC1918 addresses, it won't be affected by IPv4 exhaustion.
It might; how would a 6to4NAT affect blocking?
It's not really a 6to4 NAT per se - it's a 6to4 application level proxy. The question is, what does Squid hand off to Apache via a IPv4 back end connection if the front end connection is IPv6.
Which, frankly, I have no idea (and am off investigating...).
Q: Are we doing tproxy between the squids and apache servers?
That's the obvious not-supported situation with Squid and IPv6 with IPv4 backends.
(That would be solved by adding IPv6 addresses to the Apaches, however).