Help:Range blocks


 * See /IPv6 for information on IPv6 range blocks.

Range blocks are technical restrictions applied through Special:Block to a group of IP addresses that prevent them from editing, creating new accounts, sending email through the wiki interface, et cetera. If you check the box to prevent logged-in users from editing from these IP addresses, edits from registered accounts will also be disabled while they are connecting from the blocked range.

Range blocking is enabled and used on all Wikimedia wikis; if it is not enabled on your wiki, add " " in  (permanently enabled in MediaWiki 1.18.0 and later).

To block an IP range from Special:Block, enter the first IP address in the range followed by a forward slash and a Classless inter-domain routing (CIDR) suffix. You should avoid performing range blocks unless you understand what you are doing, or you may end up blocking tens of thousands or even millions of people who are not the problem!

This article mainly discusses IPv4; IPv6 blocks work similarly, but have different implications - see /IPv6.

Non-technical explanation
IP address are broken up into blocks of numbers. An example of this would be 148.20.57.0 through to 148.20.57.255. Once it reaches 255 the next number is 148.20.58.0.

IP addresses can be broken up in to smaller or larger blocks. The smallest practical block is a block of 4. This could be one of the following:


 * 148.20.57.0 - 148.20.57.3, or
 * 148.20.57.4 - 148.20.57.7, or
 * 148.20.57.8 - 148.20.57.11, etc.

Of each block of 4 numbers, only two can be assigned to a computer. The first and last numbers of any block are reserved for network communication. These are level 30 blocks and can be expressed like this:


 * 148.20.57.0/30</tt>, or
 * 148.20.57.4/30</tt>, or
 * 148.20.57.8/30</tt>, etc.

The next largest block is 8. They can be as follows:


 * 148.20.57.0 - 148.20.57.7</tt>, or
 * 148.20.57.8 - 148.20.57.15</tt>, or
 * 148.20.57.16 - 148.20.57.23</tt>, etc.

In this block of 8 numbers only 6 can be assigned to a computer as, once again, the first and last numbers in a block are reserved for specific uses in network communication. These can also be expressed as follows:


 * 148.20.57.0/29</tt>, or
 * 148.20.57.8/29</tt>, or
 * 148.20.57.16/29</tt>, etc.

From this point on, the number of IP addresses in a block continue to double: 16, 32, 64, 128, 256, etc.


 * A block of 16 would start 148.20.57.0/28</tt>.
 * A block of 32 would start 148.20.57.0/27</tt>.
 * A block of 64 would start 148.20.57.0/26</tt>.
 * A block of 128 would start 148.20.57.0/25</tt>.
 * A block of 256 would start 148.20.57.0/24</tt>.

So if you have an IP address and you want to block the range assigned how do you know which one to use? Let's say you have a problem with 148.20.57.34</tt>. You can lookup who has this IP address at http://arin.net/whois/?queryinput=148.20.57.34. Say this tells us that this IP address is assigned, along with a LOT of others in a /17</tt> range, to the Department of Defense. We certainly don't want to block a large block of the DoD! The rule of thumb is block as little as possible. Only block a range if there is a cluster of IP addresses giving a problem.

There's a calculator that is very useful for this: http://www.csgnetwork.com/ipinfocalc.html. Go to this site and enter  into the first set of blanks. Now select Network Prefix Length and enter  (this will give a block of 32 addresses) and click Calculate Network Information. This will show us a block of 32 IP addresses that include <tt>148.20.57.34</tt>. (The first - network - and the last - broadcast - addresses will be displayed along with the usable addresses in the range.) You can use this tool to test ranges to be sure they are what you want before entering the information to initiate the block.

Technical explanation
CIDR notation is written as the IP address, a slash, and the CIDR suffix (for example, the IPv4 "<tt>10.2.3.41/24</tt>" or IPv6 "<tt>a3:bc00::/24</tt>"). The CIDR suffix is the number of starting digits every IP address in the range have in common when written in binary.

For example: "<tt>10.10.1.32</tt>" is binary "<tt>00001010.00001010.00000001.00100000</tt>", so <tt>10.10.1.32/27</tt> will match the first 27 digits ("<tt> 00001010 . 00001010 . 00000001 . 001 00000</tt>"). The IP addresses <tt>10.10.1.32</tt>–<tt>10.10.1.63</tt>, when converted to binary, all have the same 27 first digits and will be blocked if <tt>10.10.1.32/27</tt> is blocked.

As the CIDR suffix increases, the block affects fewer IP addresses (see table of sample ranges). CIDR suffixes are not the same for IPv4 addresses as they are for IPv6 addresses; the same CIDR suffix in IPv4 blocks 296=79,228,162,514,264,337,593,543,950,336 times as many addresses in IPv6.

Calculating the CIDR suffix
You can use the table of sample ranges below to guess the range, use a computer script, or manually calculate the range.

Conversion to binary
The first step in manually calculating a range is to convert the first and last IP address to binary representation. (This assumes you're not using a computer script, which can probably calculate the range for you anyway.) An IP address is composed of four groups of eight ones and zeros. Each group represents a number from 0 to 255. To convert a number to binary, you can use a reference table or know the value of each binary digit:


 * <tt>Binary digit:  1   1   1   1   1   1   1   1</tt>
 * <tt>Value:       128  64  32  16   8   4   2   1</tt>

Proceeding from left to right, fill in <tt>1</tt> if the number is at least that value, and subtract that value (if it's not, fill in <tt>0</tt> and don't subtract). For example, to calculate 240: Thus, 240 is <tt>1111 0000</tt> because it can be represented as 128+64+32+16+0+0+0+0.
 * 1) 240 is at least 128, so place <tt>1</tt> and subtract 128.
 * 2) 112 (240-128) is at least 64, so place <tt>1</tt> and subtract 64.
 * 3) 48 (112-64) is at least 32, so place <tt>1</tt> and subtract 32.
 * 4) 16 (48-32) is at least 16, so place <tt>1</tt> and subtract 16.
 * 5) Since the remaining value is zero, all the remaining places are <tt>0</tt>.

Calculate range

 * 1) Place both IP addresses one atop the other, and count how many starting digits are exactly alike. This is the CIDR suffix.
 * 2) Double-check! Being off by one digit could extend your block by thousands of addresses.

The example below calculates the CIDR range between <tt>69.208.0.0</tt> and <tt>69.208.0.255</tt>. Note that this is a simple example; some groups of IP addresses do not so neatly fit CIDR suffixes, and need multiple different-sized blocks to block the exact range.


 * IP addresses:
 * <tt> 69.208.0.0</tt>
 * <tt> 69.208.0.255</tt>


 * Convert to binary:
 * <tt> 0100 0101.1101 0000.0000 0000.0000 0000</tt>
 * <tt> 0100 0101.1101 0000.0000 0000.1111 1111</tt>


 * Count identical first numbers:
 * <tt> 0100 0101.1101 0000.0000 0000.0000 0000</tt>
 * <tt> 0100 0101.1101 0000.0000 0000.1111 1111</tt>
 * <tt> |____________________________|</tt>
 * <tt>           24 digits</tt>


 * CIDR range:
 * <tt> 69.208.0.0/24</tt>

Table of sample ranges
The table below shows the IPv4 blocks each CIDR suffix affects. Note that MediaWiki only supports blocking CIDR suffixes 16–32 in IPv4 and 64–128 in IPv6 by default (subject to $wgBlockCIDRLimit). See /IPv6 for an IPv6 range table.