GlobalBlocking extension and IPv6
Just wondering: Since I've never seen this extension used with IPv6 nor have I seen documentation mentioning it at Extension:GlobalBlocking, I'm wondering if IPv6 is supported.
I recently read that newer MediaWiki versions would support IPv6.
I saw your edits on Extension:GlobalBlocking: As far as it does not work as expectd, you maybe want to create an issue in the bugtracker so that the developer gets informed of these shortcomings and can fix them.
>I recently read that newer MediaWiki versions would support IPv6.
Current versions do support IPv6. Whether or not a specific extension supports ipv6 is something I don't know, but core definitely should (albeit, it probably isn't that heavily tested given that Wikipedia et al doesn't have IPv6 access yet).
Core does. As an update, I've filed a Bugzilla complaint after finding that IPv6 blocks don't work.
Current status of IPv6 support on MediaWiki is documented at IPv6 support and IPv6 deployment.
IPv6 is already deployed on a few of the Uncyclopedias (Japan and Taiwan both have it, although they might get at best one or two anon-IPv6 edits in recentchanges *per week*.) If 'ansaikuropedia.org' is a top-20000 website serving one of the most IPv6-aware regions worldwide? Odds are other IPv6 MediaWiki installations are seeing even less native v6 traffic, but that's not the fault of MediaWiki, Apache, Squid/Varnish or anything in core code. The support is there. It works.
WMF is doing nothing for the www.worldipv6launch.org event, but the core software is ready.
For extensions? Affected are primarily extensions which use the IPv4/IPv6 address to check anon-IP and new registrations against lists of known spammers. Check Spambots does nothing of interest under IPv6 as it's just a wrapper around a set of existing IPv4 blacklist servers. It doesn't break anything, but there is no IPv6 blacklist to check against. CheckUser has been reported as working in IPv6. Not sure if any other extensions have been tested against spam and vandalism from IPv6 users as I've yet to see the first user IPv6-banned for doing anything particularly bad. At one or two edits per week, it might be a while... and the first one will just be special:block'ed the old-fashioned way. :)
I figured out a way to modify the db schema to allow IPv6 blocking. CheckUser's only problem concerning IPv6 is that it can't check more than /64 (and worse, I don't see a way to configure it). WMF is planning, according to a WMF comment on my talk page at enwiki, to do a stack test on that day but not a full deployment.
In IPv6, a /64 is usually one LAN (much like an IPv4 /32 is typically one LAN behind a network address translation router).
I doubt any ISP routes as finely as /128 or anything even vaguely close... even the Hurricane Electric tunnelbroker.net is a /64 or pair of /64's. The only /128's I've seen handed out are for tunnels to individual desktop PC's (gogo6 has an 'anonymous /128' as their lowest class of service, but even there everything else is at least a /64).
There was a lengthy discussion of IPv6 rangeblocks at bugzilla:24294. Odds are, they will be not the exception but the rule given that the lower eight-bytes of a sixteen-byte IP address de-facto belong not to the ISP but the end-user (at least one RFC just stuffs each computers MAC address - or any random, unique number - in there at the desktop level)
Exactly. So what if I have to check a vandal jumping around in a /48?
