Thijs/wiki.techinc.nl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Increase maximum IPv6 range block size to /19

Browse source 
Increased maximum IPv6 range block size from /32 to /19 and documented
my decision-making process. Many ISPs will be larger than /32 since /32
only allows for 64k sites at most.

Change-Id: Ia25e156fd8234519c4d74f1d41d93f94a313ce14
This commit is contained in:
Tim Starling 2012-06-08 12:26:05 +10:00 committed by Reedy
parent a99056e59c
commit dd1053bc49
1 changed files with 10 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
includes/DefaultSettings.php
View file

@ -3459,12 +3459,19 @@ $wgSysopEmailBans = true;
* Limits on the possible sizes of range blocks.
*
* CIDR notation is hard to understand, it's easy to mistakenly assume that a
* /1 is a small range and a /31 is a large range. Setting this to half the
* number of bits avoids such errors for IPv4.
* /1 is a small range and a /31 is a large range. For IPv4, setting a limit of
* half the number of bits avoids such errors, and allows entire ISPs to be
* blocked using a small number of range blocks.
*
* For IPv6, RFC 3177 recommends that a /48 be allocated to every residential
* customer, so range blocks larger than /64 (half the number of bits) will
* plainly be required. RFC 4692 implies that a very large ISP may be
* allocated a /19 if a generous HD-Ratio of 0.8 is used, so we will use that
* as our limit. As of 2012, blocking the whole world would require a /4 range.
*/
$wgBlockCIDRLimit = array(
'IPv4' => 16, # Blocks larger than a /16 (64k addresses) will not be allowed
'IPv6' => 32, # Blocks larger than a /32 (~7.9x10^28 addresses) will not be allowed
'IPv6' => 19,
);
/**