Peter Gervai wrote:
> Ehlo,
> 
> I see that this topic has been popped up from time to time since 2004,
> and that most of the misc servers have been already IPv6 enabled. I
> have checked around whether google have any info on that, and found a
> few (really few) mail on that, from the original 2004 test to a
> comment from 2008 that squid and mediawiki is the problem, apart from
> some smaller issues. (As a sidenote, google don't seem to find
> anything on site:lists.wikimedia.org about "ipv6", interesting.)

List archives are not searchable by google.

> Now, squid fully supports IPv6 as of now (since 3.1), so I guess
> that's check. (I didn't try it, though, but others seem to have.)
> 
> MediaWiki, well, http://www.mediawiki.org/wiki/IPv6_support didn't
> mention any outstanding problem and the linked bug is closed, so as
> far as I'm observing (without actually testing it) it looks okay.
> 
> The database structure may require some tuning as far as I see. Right?

I don't think so.

MediaWiki code may need some assumptions about it, though.

> Apache handle it since eternity, php does I guess.
> 
> Are there any further, non v6 compatible components in running a
> wikipedia? If not, is there any outstanding proble which would make it
> impossible to fire up a test interface on ipv6?
> 
> I'd say to use a separate host, like en.ipv6.wikipedia.org, and not to
> worry about the cache efficiency because I doubt that the ipv6 level
> traffic would really measure up to the ipv4 one. At least it could be
> properly measured, and decision should base on facts how to go on.
> 
> Maybe there's a test host already on, but I wasn't able to find it, so
> I guess nobody else can. ;-)

I think this comment in the config summarises it:
"no IPv6 support - 20051207"

> Is there any further problem in this topic require solutions, or it
> just didn't occur to anyone lately?
> 


_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to