IPv4 Special Addresses (2) — Private, CGN, Multicast, Reserved
This lesson covers the blocks that make the Internet scale. RFC 1918 gives every home and business the same addresses behind a NAT; RFC 6598 gives ISPs a separate shared block; and two huge ranges are set aside for multicast and future use. Get the ranges exact — they are asked verbatim.
Private addresses — RFC 1918
RFC 1918 (1996) reserves three address blocks for use inside private networks. These are the private addresses, and every home router on Earth uses them:
| Block | Exact range | Made of | Size |
|---|---|---|---|
| 10.0.0.0/8 | 10.0.0.0 – 10.255.255.255 | one /8 | 16,777,216 addresses |
| 172.16.0.0/12 | 172.16.0.0 – 172.31.255.255 | 16 × /16 | 1,048,576 addresses |
| 192.168.0.0/16 | 192.168.0.0 – 192.168.255.255 | 256 × /24 | 65,536 addresses |
Two details are exam traps:
172.16.0.0/12is NOT the whole of 172.x. Only the second octet values 16 through 31 are private: 172.16.0.0 through 172.31.255.255. An address such as172.15.0.1or172.32.0.1is not private.10.0.0.0/8is a single /8 — it covers the entire first octet value 10.
Private addresses are not globally routable. A router on the public Internet will not forward a packet whose destination is a private address; if one ever leaks out, it is dropped. That is deliberate: the same private ranges can be reused in millions of separate networks without conflict.
Why private addresses exist — and NAT
IPv4 has about 4.29 billion addresses and they ran out for practical purposes years ago. Private addressing is one of the two big reasons the Internet kept growing anyway (the other is NAT, which goes hand in hand with it).
The idea is simple. Inside a network, hosts only need to talk to each other and to get out to the Internet. They do not each need a globally unique address. So we give every internal host a private address from RFC 1918, and we let many hosts, in many different organisations, use the same private numbers. The overlap never matters because the private addresses never travel across the Internet.
The device that makes this work is NAT (Network Address Translation), specified in RFC 3022. A NAT router sits at the boundary of the private network. When an internal host sends traffic outward, the router:
- Rewrites the source private address to the router’s public address as the packet leaves.
- Records the translation in a table.
- On the reply, looks up the table and rewrites the destination back to the original private address.
Because most home and small-office NAT also tracks port numbers, one public address can serve hundreds of internal hosts at once (this port-based form is often called PAT or NAT overload). The internal topology stays hidden — a useful side effect for security.
Shared address space — CGN (RFC 6598)
RFC 6598 reserves one more block, not for end-user private networks but for use between an ISP and its Carrier-Grade NAT (CGN):
100.64.0.0/10 — the range 100.64.0.0 through
100.127.255.255 (4,194,304 addresses). Used between an ISP and a subscriber’s
CGN device.Why it exists: an ISP often runs its own NAT (CGN) to share a limited pool of public addresses
among many subscribers. The addresses on the segment between the ISP and the customer’s router
must be unique among those subscribers but need not be globally routable. RFC 6598 created
100.64.0.0/10 for exactly that job.
Two things to keep straight for the exam:
100.64.0.0/10is NOT RFC 1918 private. It is a separate shared block with a different purpose and a different RFC (6598).- It is not globally routable: an ISP must not advertise it to the Internet,
and a packet to a
100.64.x.xaddress should never cross the public Internet.
100.0.0.0/8 range used for some carrier and government networks. The CGN shared
space is only the /10: 100.64.0.0 – 100.127.255.255.Multicast — 224.0.0.0/4
Block: 224.0.0.0/4 — the range 224.0.0.0 through
239.255.255.255. This is the IPv4 multicast space (historically
“Class D”), defined in RFC 1112 with allocation guidance in RFC 3171.
A multicast address does not name one host; it names a group. A single packet sent to a multicast address is delivered by the network to every host that has joined that group. Multicast is used for one-to-many traffic such as IPTV, routing-protocol hellos, and video conferencing — it is far more efficient than unicasting the same stream once per receiver.
The 224.0.0.0/24 slice is the link-local multicast range: those
packets stay on the local segment and are never forwarded by a router. Multicast addresses are
never a valid source address — a host always sources traffic from a unicast
address.
Reserved for future — 240.0.0.0/4
Block: 240.0.0.0/4 — the range 240.0.0.0 through
255.255.255.255, historically “Class E”. This space is reserved
for future use (experimental) and is not available for normal assignment;
routers must not forward it as ordinary unicast traffic.
The block’s last address, 255.255.255.255, is special even
within this range: it is the limited broadcast address (RFC 919/922), delivered to
all hosts on the local subnet and never forwarded — as covered in Lesson 5. So the full
240.0.0.0/4 block is reserved, and one address inside it has an additional, specific
function.
Private vs CGN vs link-local
These three get confused constantly, so learn the differences by range and RFC:
| Type | Exact range(s) | RFC | Where used | Globally routable? |
|---|---|---|---|---|
| Private | 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 | 1918 | Home / enterprise LANs | No — needs NAT (RFC 3022) |
| CGN shared | 100.64.0.0/10 | 6598 | Between ISP and subscriber CGN | No |
| Link-local | 169.254.0.0/16 | 3927 | Auto-config on a single link (no DHCP) | No |
Notice they are three different mechanisms: RFC 1918 private addressing is for building your own reusable network; RFC 6598 shared addressing is for carriers; RFC 3927 link-local is a fallback when a host cannot get an address at all. None of the three is globally routable, and none should ever appear as a destination on the public Internet.
100.64.0.0/10 as “private.” It is
not RFC 1918 private — it is the RFC 6598 CGN shared block. Only
10/8, 172.16/12, 192.168/16 are private.Key terms
| Term | Meaning |
|---|---|
| Private address | An RFC 1918 address (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) for use inside a private network; not globally routable. |
| NAT | Network Address Translation (RFC 3022); rewrites private source addresses to a public address at the network edge. |
| CGN shared address space | The RFC 6598 block 100.64.0.0/10, used between an ISP and a Carrier-Grade NAT; not RFC 1918 private. |
| Multicast | The IPv4 block 224.0.0.0/4; delivers one packet to a group of interested hosts (RFC 1112). |
| Reserved for future use | The IPv4 block 240.0.0.0/4 (240.0.0.0 – 255.255.255.255), historically Class E; not for normal assignment. |
Review
Check what you have learned with these review questions.
Sources & references
- Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G. J. & Lear, E. RFC 1918: Address Allocation for Private Internets (1996). rfc-editor.org/rfc/rfc1918.
- Srisuresh, P. & Egevang, K. RFC 3022: Traditional IP Network Address Translator (Traditional NAT) (2001). rfc-editor.org/rfc/rfc3022.
- Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C. & Azinger, M. RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space (2012). rfc-editor.org/rfc/rfc6598.
- Deering, S. RFC 1112: Host Extensions for IP Multicasting (1989); see also Albanna, Z. et al. RFC 3171 (2001). rfc-editor.org/rfc/rfc1112.
- Cisco. CCNA (200-301) Exam Topics, IP Addressing. cisco.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.