Page MenuHomePhabricator

Local IPv6 rangeblock on mediawiki.org does not work?
Closed, ResolvedPublic

Description

When I attempted a /60 rangeblock of proxies and unblocked the single IPv6 address, the proxy I attempted to catch in the rangeblock did not get blocked by the rangeblock. This is clearly a MediaWiki problem because a global block using Extension:GlobalBlocking of the exact same range was effective.


Version: unspecified
Severity: major
URL: https://www.mediawiki.org/w/index.php?title=Special%3ALog&type=block&user=Jasper+Deng&page=&year=&month=-1&tagfilter=

Details

Reference
bz37481

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 12:26 AM
bzimport set Reference to bz37481.
bzimport added a subscriber: Unknown Object (MLST).

(The local wiki is MediaWiki.org using 1.20wmf5; the global block was made by stewards)

Was the /60 rangeblock local or global?
Can you provide some IPv6 addresses to illustrate the problem (feel free to email me if you don't want to post them here)?
Does this problem happen also when no GlobalBlocking is involved (for example on a small local installation of MediaWiki)?

This is probably a 1.20 regression, because 1. this worked properly in MediaWiki 1.17, 2. the block was local on MediaWiki.org, 3. the particular range was used by 1proxy.de, 2proxy.de, 3proxy.de, and 4 proxy.de and it was 2001:4BA0:FFF9:170:0:0:0:0/60.

I doubt GlobalBlocking is the problem here. I don't know if I can reproduce it on my own wikis since they don't use 1.20wmf5.

Simple /60 IPv6 rangeblock works on my test trunk wiki.

Adding URL to mediawiki.org block log since the original sequence was a bit more complex.

I reproduced it on testwiki:
http://test.wikipedia.org/w/index.php?title=Talk%3AMain_Page&diff=151859&oldid=151192
Although the /44 range was locally blocked, that edit was allowed after I temporarily disabled both global blocks affecting it.

Tim Starling resolved bug 41778, is this now fixed as well?

<Jasper_Deng> Krenair: yep, that bug is now fixed too