In the Internet addressing architecture, a private network is a network that uses private IP address space, following the standards set by RFC 1918 for Internet Protocol Version 4 (IPv4), and RFC 4193 for Internet Protocol Version 6 (IPv6). These addresses are commonly used for home, office, and enterprise local area networks (LANs). Private IP address spaces were originally defined in an effort to delay IPv4 address exhaustion, but they are also a feature of IPv6 where exhaustion is not an issue.
Addresses in the private space are not allocated to any specific organization and anyone may use these addresses without approval from a regional Internet registry. However, IP packets addressed from them cannot be transmitted through the public Internet, and so if such a private network needs to connect to the Internet, it must do so via a network address translator (NAT) gateway, or a proxy server.
Private IPv4 address spaces
|RFC1918 name||IP address range||number of addresses||largest CIDR block (subnet mask)||host id size||mask bits||classful description[Note 1]|
|24-bit block||10.0.0.0 – 10.255.255.255||16,777,216||10.0.0.0/8 (255.0.0.0)||24 bits||8 bits||single class A network|
|20-bit block||172.16.0.0 – 172.31.255.255||1,048,576||172.16.0.0/12 (255.240.0.0)||20 bits||12 bits||16 contiguous class B networks|
|16-bit block||192.168.0.0 – 192.168.255.255||65,536||192.168.0.0/16 (255.255.0.0)||16 bits||16 bits||256 contiguous class C networks|
Users can randomly assign networks and subnets from the above ranges, however as the space is relatively small this can create conflicts when merging (see below).
Dedicated space for carrier grade NAT deployments
In April 2012, IANA allocated 100.64.0.0/10 for use in carrier-grade NAT scenarios in RFC 6598. This address block should not be used either on private networks or on the public Internet: it is intended only for use within the internal operations of carrier networks. The size of the address block (222, approximately 4 million, addresses) was selected to be large enough to uniquely number all customer access devices for all of a single operator's points of presence in a large metropolitan area such as Tokyo.
Private IPv6 addresses
The address block fc00::/7 has been reserved by IANA as described in RFC 4193. These addresses are called Unique Local Addresses (ULA). They are defined as unicast addresses, and contain a 40-bit random number in the routing prefix to prevent collisions when two private networks are interconnected. Despite being inherently local in usage, the IPv6 address scope of unique local addresses is global.
The first block defined is fd00::/8, designed for /48 routing blocks, in which users can create multiple subnets as needed.
|RFC 4193 Block||Prefix/L||Global ID (random)||Subnet ID||Number of addresses in subnet|
|48 bits||16 bits||64 bits|
|Prefix/L||Global ID (random)||Subnet ID||Interface ID||Address||Subnet|
A former standard proposed the use of site-local addresses in the fec0::/10 block, but because of scalability concerns and poor definition of what constitutes a site, its use has been deprecated since September 2004 by RFC 3879.
Another type of private networking uses the link-local address range. The validity of link-local addresses is limited to a single link; e.g. to all computers connected to a switch, or to one wireless network. Hosts on different sides of a bridge are also on the same link, whereas hosts on different sides of a router are on different links.
In IPv4, link-local addresses are codified in RFC 6890 and RFC 3927. Their utility is in zero configuration networking when Dynamic Host Configuration Protocol (DHCP) services are not available and manual configuration by a network administrator is not desirable. The block 169.254.0.0/16 is reserved for this purpose, with the exception of the first and the last /24 subnets in the range. If a host on an IEEE 802 (Ethernet) network cannot obtain a network address via DHCP, an address from 169.254.1.0 to 169.254.254.255 may be assigned pseudorandomly. The standard prescribes that address collisions must be handled gracefully.
In IPv6, link-local addresses are codified in RFC 4862. Their use is mandatory, and an integral part of the IPv6 standard. The architecture defined in RFC 4291 sets aside the block fe80::/10 for IP address autoconfiguration.
The most common use of private addresses is in residential IPv4 networks, since most Internet service providers (ISPs) allocate only a single publicly routable IPv4 address to each residential customer, but many homes have more than one computer or other Internet connected device, such as smartphones. In this situation, a network address translator (NAT/PAT) gateway is usually used to provide Internet connectivity to multiple hosts.
Private addresses are also commonly used in corporate networks, which for security reasons, are not connected directly to the Internet. Often a proxy, SOCKS gateway, or similar devices are used to provide restricted Internet access to network-internal users.
In both cases, private addresses are often seen as enhancing network security for the internal network, since it is difficult for an Internet (external) host to connect directly to an internal system.
It is common for packets originating in private address spaces to be misrouted onto the Internet. Private networks often do not properly configure DNS services for addresses used internally and attempt reverse DNS lookups for these addresses, causing extra traffic to the Internet root nameservers. The AS112 project attempted to mitigate this load by providing special blackhole anycast nameservers for private address ranges which only return negative result codes (not found) for these queries.
Organizational edge routers are usually configured to drop ingress IP traffic for these networks, which can occur either by misconfiguration, or from malicious traffic using a spoofed source address. Less commonly, ISP edge routers drop such egress traffic from customers, which reduces the impact to the Internet of such misconfigured or malicious hosts on the customer's network.
Merging private networks
Since the private IPv4 address space is relatively small, many private IPv4 networks use the same address space. This can create a problem when merging such networks, namely the duplication of addresses on multiple devices. In this case, networks or hosts must be renumbered, often a time-consuming task, or a network address translator must be placed between the networks to masquerade the duplicated addresses.
To mitigate this problem for IPv6, RFC 4193 specifies a large (40-bit, which has a keyspace of about a trillion) unique Global ID to be pseudo-randomly generated by each organization using Unique Global Addresses. It is very unlikely that two network addresses generated in this way will be the same.
Private use of other reserved addresses
- RFC 1918 – "Address Allocation for Private Internets"
- RFC 2036 – "Observations on the use of Components of the Class A Address Space within the Internet"
- RFC 2050 – "Internet Registry IP Allocation Guidelines"
- RFC 2101 – "IPv4 Address Behaviour Today"
- RFC 2663 – "IP Network Address Translator (NAT) Terminology and Considerations"
- RFC 3022 – "Traditional IP Network Address Translator (Traditional NAT)"
- RFC 3330 – "Special-Use IPv4 Addresses" (superseded)
- RFC 3879 – "Deprecating Site Local Addresses"
- RFC 3927 – "Dynamic Configuration of IPv4 Link-Local Addresses"
- RFC 4193 – "Unique Local IPv6 Unicast Addresses"
- RFC 5735 – "Special-Use IPv4 Addresses" (superseded)
- RFC 6598 – "Reserved IPv4 Prefix for Shared Address Space"
- RFC 6890 – "Special-Purpose IP Address Registries"
- Classful addressing is obsolete and has not been used in the Internet since the implementation of Classless Inter-Domain Routing (CIDR), starting in 1993. For example, while 10.0.0.0/8 was a single class A network, it is common for organizations to divide it into smaller /16 or /24 networks. Contrary to a common misconception, a /16 subnet of a class A network is not referred to as a class B network. Likewise, a /24 subnet of a class A or B network is not referred to as a class C network. The class is determined by the first three bits of the prefix.
- "RFC 1918: Address Allocation for Private Internets". IETF. February 1996. p. 4.
- Forouzan, Behrouz (2013). Data Communications and Networking. New York: McGraw Hill. pp. 530–31. ISBN 978-0-07-337622-6.
- "RFC 6598: Reserved IPv4 Prefix for Shared Address Space". IETF. April 2011. p. 8.