PracticeLabs
Week 1Lesson 6Required8 min estimated0% progress

IPv4 Addresses & Private Ranges

Read the structure of an IPv4 address, tell a normal host address from a reserved one, and recognise the private ranges every network in the world reuses.

Lesson orientation

What you'll learn (4 objectives)~8 min: video → lesson → check → apply → lab prep

Learning objectives

  • Describe an IPv4 address as 32 bits split into a network portion and a host portion by its mask
  • Recognise the three RFC 1918 private ranges in both dotted-decimal and CIDR form
  • Distinguish private, public, loopback, and link-local addresses on sight
  • Explain why a device with a private address needs NAT to reach the public Internet

Terms you will see

IPv4OctetSubnet maskCIDR prefixPublic addressPrivate addressRFC 1918NATLoopbackLink-localAPIPA

Time breakdown

  • Read the notes5 min
  • Classify the addresses3 min

Assigned video

Opens on YouTube
Optional video

IPv4 Addressing Part 1 (Day 7)

By Jeremy's IT Lab · Opens externally on YouTube

Watch time not yet confirmed for this video — the notes below cover everything this lesson requires.

Where to stop

Stop as soon as the video starts converting octets into binary. Everything from that point on — binary conversion, subnet math, VLSM — belongs to Week 2, and meeting it here tends to make the simple idea in this lesson harder rather than easier.

The exact timestamp of that stop point has not been confirmed by a human yet, so none is shown. Go by the topic change, not by a clock reading.

The link opens in a new browser tab. Return here when you finish watching.

Watch for these concepts

  • The address broken into its four octets
  • How the mask marks where the network portion ends
  • The three private ranges and their boundaries

Go beyond the video

The assigned video introduces the idea. CCNA Practice Labs completes the learning path: clarify core concepts, explore how each device behaves, visualize the communication path, check your understanding, and prepare for hands-on lab work.

Watch the concept → understand it → visualize it → practice it → apply it.

An IPv4 address is 32 bits in four parts

An IPv4 address is 32 bits long, written as four octets — four groups of 8 bits — separated by dots. Eight bits can express 256 values, so each octet runs from 0 to 255. That is why 192.168.10.45 is a valid address and 192.168.10.300 is not.

The address on its own is only half the story. Lesson 2 introduced the subnet mask as the thing that tells a device which leading part of an address identifies the network and which trailing part identifies the individual device on it. The mask is written either in full, as 255.255.255.0, or as a CIDR prefix — a slash and the number of network bits, as in /24. A /24 means the first 24 bits name the network and the remaining 8 name the host within it.

Concept now, arithmetic in Week 2
This lesson stops at the idea: the mask decides where the network portion ends and the host portion begins. Converting octets to binary, working out how many hosts a mask allows, and splitting a network into smaller ones are the whole subject of Week 2. You do not need any of that yet, and trying to learn it now tends to obscure the simpler point.

Private and public addresses

Most IPv4 addresses are public: globally unique, allocated by a registry, and routable across the Internet. But three blocks are set aside by a standard called RFC 1918 for private use. Any organisation may use them on its internal network without asking anyone, and no router on the public Internet will carry them.

That is a deliberate trade. Because everybody reuses the same private space, the world does not run out of addresses nearly as fast — but a device holding a private address cannot be reached from the Internet directly. It gets there through NAT, Network Address Translation, performed by the router at the network edge, which swaps the private source address for a public one on the way out and reverses the swap on the way back. Why it is needed is the point here; how it works is a later lesson in IP Services.

The ranges to recognise on sight

Private and special-use ranges — the rest of the course refers back to this table
BlockRangeCIDR
Private (large)10.0.0.0 – 10.255.255.25510.0.0.0/8
Private (medium)172.16.0.0 – 172.31.255.255172.16.0.0/12
Private (small)192.168.0.0 – 192.168.255.255192.168.0.0/16
Loopback127.0.0.0 – 127.255.255.255127.0.0.0/8
Link-local (APIPA)169.254.0.0 – 169.254.255.255169.254.0.0/16

The loopback range is the device talking to itself; 127.0.0.1 in particular never leaves the machine, which makes it useful for testing whether the local networking stack works at all. The link-local range, also called APIPA, is what a host assigns itself when it asks for an address by DHCP and nothing answers. That makes it a diagnostic in its own right: seeing a 169.254 address on a machine is a strong signal that DHCP failed, not that someone configured it oddly.

The one everybody misreads
The middle private block is 172.16.0.0/12, and the /12 means it spans 172.16 through 172.31 — not just 172.16. So 172.20.5.1 is a private address, and 172.32.5.1 is a public one. This distinction appears on the exam more often than its size warrants.

What you should retain

  • An IPv4 address is 32 bits in four octets, each 0 to 255.
  • The mask, written in full or as a CIDR prefix, splits the address into a network portion and a host portion.
  • The private ranges are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 — reused everywhere, routed nowhere on the public Internet.
  • NAT at the network edge is what lets a privately addressed device reach the Internet.
  • 127.0.0.0/8 is loopback. A 169.254 address means DHCP did not answer.

This is the on-ramp to Week 2, which opens by turning the mask from an idea into arithmetic you can do on paper.

Pause and predictNot scored — nothing is recorded

Before you read on

Classify each of these as public, private, loopback, or link-local: 10.200.14.6 · 172.20.5.1 · 8.8.8.8 · 169.254.10.10

Interactive tool
Optional~6 min

Binary, Hex & Addressing Lab

Optional preparation for Week 2 rather than work for this lesson. If you want a head start on reading octets before the subnetting material arrives, this is where to get it.

Study deeper

Topic guides extend this lesson — they do not replace the first-party walkthrough above.

IP Addressing & Subnetting

For the IPv4 header walk and the classful A/B/C background — and it is where Week 2's subnetting work starts