Week 6 · Lesson 6

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.

CCNA 200-301 IPv4 Addressing Verified 2026-10-11
Part 1

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:

BlockExact rangeMade ofSize
10.0.0.0/810.0.0.0 – 10.255.255.255one /816,777,216 addresses
172.16.0.0/12172.16.0.0 – 172.31.255.25516 × /161,048,576 addresses
192.168.0.0/16192.168.0.0 – 192.168.255.255256 × /2465,536 addresses

Two details are exam traps:

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.

Exam tip. Memorise the RFC 1918 blocks cold: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16. The only common mistake is quoting 172.16.0.0/16 or 172.0.0.0/8 — the correct mask is /12, spanning 172.16.0.0 to 172.31.255.255.
Is it private? · type an address

Part 2

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:

  1. Rewrites the source private address to the router’s public address as the packet leaves.
  2. Records the translation in a table.
  3. 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.

Definition — private address. An address from 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16 (RFC 1918), used only inside a private network, never routed on the public Internet, and translated to a public address by NAT (RFC 3022) at the network edge.
Internet Home router NAT (RFC 3022) inside 192.168.1.1 PC A 192.168.1.10 PC B 192.168.1.11 Web server SRC 192.168.1.10:5000 → public :6000 Private side (RFC 1918): hosts share one public address. Public side: the outside IP is leased from the ISP.
NAT translation table · select an inside host
Inside hostInside portOutside addressOutside port

Part 3

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):

Shared address space. 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:

Note. Do not confuse the 100.64.0.0/10 CGN block with the older, unrelated 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.
Part 4

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.

Well-known multicast groups · pick one

Part 5

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.

Part 6

Private vs CGN vs link-local

These three get confused constantly, so learn the differences by range and RFC:

TypeExact range(s)RFCWhere usedGlobally routable?
Private10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/161918Home / enterprise LANsNo — needs NAT (RFC 3022)
CGN shared100.64.0.0/106598Between ISP and subscriber CGNNo
Link-local169.254.0.0/163927Auto-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.

Exam tip. A favourite trick is to offer 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.
Compare the three · select a type

Key terms

TermMeaning
Private addressAn 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.
NATNetwork Address Translation (RFC 3022); rewrites private source addresses to a public address at the network edge.
CGN shared address spaceThe RFC 6598 block 100.64.0.0/10, used between an ISP and a Carrier-Grade NAT; not RFC 1918 private.
MulticastThe IPv4 block 224.0.0.0/4; delivers one packet to a group of interested hosts (RFC 1112).
Reserved for future useThe IPv4 block 240.0.0.0/4 (240.0.0.0 – 255.255.255.255), historically Class E; not for normal assignment.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. 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.
  2. Srisuresh, P. & Egevang, K. RFC 3022: Traditional IP Network Address Translator (Traditional NAT) (2001). rfc-editor.org/rfc/rfc3022.
  3. 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.
  4. Deering, S. RFC 1112: Host Extensions for IP Multicasting (1989); see also Albanna, Z. et al. RFC 3171 (2001). rfc-editor.org/rfc/rfc1112.
  5. 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.