Study guide
IPv4 Classes, Private/Public, APIPA, and Loopback
CompTIA Network+ N10-009
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
Current Exam Facts and Applied Networking Judgment Official Domain Weights and an 8-12 Week Study Plan How to Use Labs, Practice, and PBQ Workflow Missed-Question Notebook and Final Readiness Metrics
2 Domain 1: Networking Concepts (23%)
OSI and TCP/IP Models with Device and Protocol Mapping Networking Appliances and Where They Operate Ports and Protocol Decision Table Traffic Types and Encapsulation Flow
3 Domain 1: Media, Connectors, Transceivers, and Network Architectures
Copper, Fiber, Coax, and DAC Media Connector and Transceiver Selection Network Topologies and Design Patterns Cloud and Virtual Networking Concepts
4 Domain 1: IP Addressing and Subnetting Mastery
IPv4 Classes, Private/Public, APIPA, and Loopback CIDR, VLSM, and Subnet Math IPv6 Address Types and Notation Routing Basics and Longest Prefix Match
5 Domain 2: Network Implementation - Routing
Static vs Dynamic Routing and Route Selection OSPF, EIGRP, and BGP Basics at Network+ Depth NAT/PAT, VIP/FHRP, and Subinterfaces Routing PBQs and Troubleshooting Route Table Clues
6 Domain 2: Network Implementation - Switching
VLANs, Access Ports, Trunks, and Native VLAN STP/RSTP Loop Prevention and Bridge Roles Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings Switch Implementation PBQs and Common Misconfigurations
7 Domain 2: Network Implementation - Wireless and Physical Implementation
Wi-Fi Standards, Bands, and Channels SSID Security, Guest Networks, and Authentication Antennas, Coverage, Roaming, Interference, and Site Surveys Physical Installation Implications
8 Domain 2: Network Implementation - Services Implementation
DNS Record Types and Troubleshooting Cues DHCP, DHCPv6, SLAAC, Scopes, Leases, and Relay NTP, PTP, NTS, and Time-Sensitive Networking Service Implementation PBQs: DNS, DHCP, VLANs, and Firewall Direction
9 Domain 3 Part A: Network Operations Documentation and Governance
Physical, Logical, Rack, Cable, Wireless Diagrams, and IPAM Asset Inventory, Baselines, SLAs, SOPs, and Runbooks Change Management and Request Tracking Lifecycle, EOL, EOS, Decommissioning, and Configuration Management
10 Domain 3 Part B: Monitoring, Remote Access, and Resilience
SNMP, Flow, Syslog, Packet Capture, Log Aggregation, APIs, and Port Mirroring Baselines and Performance Metrics Remote Access, Management Paths, and Secure Admin Habits DR and HA Concepts: RPO, RTO, MTTR, MTBF, Sites, Failover, and Testing
11 Domain 4: Logical Security and Secure Access (14%)
Encryption in Transit, Encryption at Rest, PKI, and Certificates IAM, MFA, SSO, Directory Services, and AAA Authorization, Least Privilege, RBAC, Geofencing, and Time-Based Access VPNs and Secure Management Design
12 Domain 4: Segmentation, Risk, and Network Attacks (14%)
Segmentation for Guest, BYOD, IoT, IIoT, SCADA, ICS, and OT Risk, Compliance, Audit, Data Locality, PCI, and GDPR Network Attacks and Scenario Cues Attack-to-Mitigation PBQ Tables
13 Domain 4: Security Controls and Hardening (14%)
Firewalls, IDS, IPS, Security Zones, and Screened Subnets ACLs, Filtering, NAC, Hardening, and Key Management Deception Technologies and Physical Security Zero Trust, SASE, and Trusted or Untrusted Zone Decisions
14 Domain 5: Troubleshooting Methodology and Tools (24%)
Official Troubleshooting Methodology and Evidence Handling Command-Line Tools: ping, traceroute, nslookup, dig, ipconfig, ifconfig, ip, arp, netstat, ss, and route Packet, Protocol, and Wi-Fi Analyzers Choosing the Right Tool by Symptom PBQs
15 Domain 5: Physical, Interface, and Wireless Troubleshooting (24%)
Cable Issues: Type, Attenuation, Crosstalk, Termination, and TX/RX Interface Issues: Errors, Discards, Duplex, Speed, Port Status, and PoE Transceiver, Fiber, and Signal Strength Troubleshooting Wireless Troubleshooting: Interference, Channels, Roaming, RSSI/SNR, Security, and Captive Portals
16 Domain 5: Network Services, Switching, Routing, and Performance Troubleshooting (24%)
DHCP, DNS, NTP, and IP Addressing Issues VLAN, STP, Trunk, Native VLAN, and ACL Issues Routing, Default Gateway, Route Table, and NAT Issues Congestion, Latency, Jitter, Packet Loss, and Application Performance Clues
17 Performance-Based Question Labs
Subnetting and VLSM Design Lab VLAN, Trunk, Router-on-a-Stick, and Firewall Rule Lab Wireless Deployment and Troubleshooting Lab Monitoring, Log Triage, and Route or Service Troubleshooting Lab
18 High-Yield Reference and Final Study Plan
High-Yield Ports and Protocols Table Wi-Fi, Cabling, Connectors, and Transceivers Quick Table Acronyms and Command-Line Tool Quick Table Final 7-Day Review Plan and Readiness Checklist
19 Final Synthesis: Strategy, Remediation, and Readiness
Mixed-Set Decision Strategy for Qualifiers and Close Answers Missed-Question Remediation Notebook by Error Type Exam-Day Time Management and PBQ Order 100-Question Readiness Simulation Blueprint Mapped to N10-009 Weights
IPv4 Classes, Private/Public, APIPA, and Loopback
Key Takeaways Explain This Topic AI
IPv4 addresses are 32-bit values written as four decimal octets, but the subnet mask, not the first octet, defines the network boundary on modern networks.
Legacy classes A through E are recognition trivia; CIDR governs real subnetting, so never assume a mask from the first octet unless the question explicitly invokes classful addressing.
The three RFC 1918 private ranges are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16, and they require NAT to reach the public internet.
Automatic Private IP Addressing (APIPA) in 169.254.0.0/16 is a self-assigned link-local address that almost always means a DHCP failure.
Loopback 127.0.0.0/8 (commonly 127.0.0.1) tests the local TCP/IP stack and never leaves the host or represents a remote device.
Last updated: June 2026
IPv4 Addressing on the N10-009 Exam
IPv4 addressing is foundational for CompTIA Network+ N10-009 , the current edition launched in 2024. The exam delivers up to 90 questions in 90 minutes , mixes multiple-choice with performance-based questions (PBQs) , and requires a scaled score of 720 on the 100-900 scale to pass (not a fixed number of items correct). The exam fee in the United States is about $369 USD . Subnetting and address recognition appear across multiple domains, so you must read a leading octet or a self-assigned address and instantly name its type.
N10-009 uses five official domains with these weights. Address topics live mostly in Networking Concepts but resurface heavily in Troubleshooting.
- Domain Name Weight
- 1.0 Networking Concepts 23%
- 2.0 Network Implementation 20%
- 3.0 Network Operations 19%
- 4.0 Network Security 14%
- 5.0 Network Troubleshooting 24%
An IPv4 address is a 32-bit number written as four 8-bit octets , each 0-255, separated by dots. The subnet mask marks which leading bits are the network portion and which trailing bits identify the host. Two reserved addresses exist in every subnet: the network ID (all host bits 0, the first address) and the broadcast address (all host bits 1, the last address). Neither is assignable to a host.
- Term Meaning Example
- IPv4 address 32-bit dotted-decimal value 192.168.10.25
- Octet One 8-bit field, 0-255 192
- Subnet mask Splits network bits from host bits 255.255.255.0
- CIDR prefix Slash notation for mask length /24
- Network ID First (reserved) address 192.168.10.0/24
- Broadcast Last (reserved) address 192.168.10.255/24
- Usable hosts Addresses between the two 192.168.10.1-192.168.10.254
- Legacy Classes
Classful addressing predates CIDR but the first-octet ranges still appear in questions. Recognize the range, then ignore the default mask unless the question is explicitly about classes.
- Class First octet Default mask Historical use
- A 1-126 /8 Very large networks
- B 128-191 /16 Medium networks
- C 192-223 /24 Small networks
- D 224-239 none Multicast
- E 240-255 none Experimental/reserved
Note the gap: 127.x.x.x is reserved for loopback , so the Class A host range stops at 126. The address 0.0.0.0 is special and means "this host," "any address," or the default route depending on context, never a normal host.
Private, Public, APIPA, and Loopback
- Range Type What it tells you
- 10.0.0.0/8 Private (RFC 1918) Internal; NATed to reach the internet
- 172.16.0.0/12 Private Spans 172.16.0.0-172.31.255.255
- 192.168.0.0/16 Private Common home/SOHO range
- 169.254.0.0/16 APIPA / link-local DHCP failed on an IPv4 client
- 127.0.0.0/8 Loopback Local stack test only
- 224.0.0.0/4 Multicast One-to-many delivery group
- Everything else Public ISP/registry-assigned, internet-routable
The most common trap is the 172.16.0.0/12 boundary: 172.20.5.6 is private but 172.40.5.6 is public , because the private block ends at 172.31. The exam loves testing whether you stop counting at 31.
Troubleshooting Clues
A host's address often diagnoses the fault before you run a single command.
- Symptom Interpretation
- Address is 169.254.23.44 DHCP unreachable; client self-assigned APIPA
- Pings 127.0.0.1 but not the gateway Local stack is fine; check NIC, cable, VLAN, gateway
- Has 192.168.1.25, gateway 192.168.2.1/24 Gateway is outside the local subnet
- Two hosts share one IP Duplicate IP conflict
- Public IP where private expected Wrong DHCP scope or static misconfiguration
- PBQ-Style Thinking
Scenario: a workstation shows 169.254.77.19 / 255.255.0.0 and cannot reach file shares or the internet. APIPA is the symptom , not the cause. Check DHCP server availability, the IP-helper/relay configuration on the router, the VLAN assignment on the switch port, link status, and wireless association. Restoring DHCP fixes the address.
Scenario: a printer at 192.168.10.50/24 has gateway 192.168.11.1 . It talks to local hosts but cannot leave the subnet, because the gateway is not inside 192.168.10.0/24. Correct the gateway so it sits on the local network.
Why the Mask Matters More Than the Class
A persistent exam trap is reading the first octet and assuming a default mask. Consider 10.10.10.10. By classful logic it is a Class A address with a /8 mask, yet in a real network it might be configured as 10.10.10.10/24 or 10.10.10.10/30. The class tells you nothing reliable about the subnet boundary; only the mask or prefix does. CompTIA writes distractors precisely to punish candidates who answer from the class table instead of the supplied mask. Whenever a question gives both a first octet and an explicit prefix, the prefix always governs the network and host split.
The same caution applies to public versus private classification. Private status is a function of the documented RFC 1918 ranges, not of any class. The Class A range spans 1-126 in the first octet, but only 10.0.0.0/8 inside it is private; 11.0.0.0/8 through 126.0.0.0/8 are public. Likewise the bulk of Class B and Class C space is public, with just 172.16.0.0/12 and 192.168.0.0/16 carved out as private. Memorize the three private blocks as fixed facts and treat everything else outside the loopback, APIPA, and multicast reservations as public.
Address Recognition Drill
Drill these until classification is instant, because the exam expects sub-five-second recognition on PBQ scenarios where address type is the whole answer.
- Address Classification
- 10.44.3.2 Private
- 172.20.5.6 Private
- 172.40.5.6 Public (past 172.31)
- 192.168.100.10 Private
- 169.254.8.9 APIPA / link-local
- 127.0.0.1 Loopback
- 224.0.0.5 Multicast
Finally, remember the practical chain of evidence APIPA gives you on a real call. A user reports "no internet," you check ipconfig, and you see a 169.254 address. That address is the system telling you it asked for a lease and got silence. The fault is never APIPA itself; it is whatever sits between the client and the DHCP server, such as a down DHCP service, an unconfigured IP helper on the router, a blocked UDP 67/68 path, a misassigned VLAN, or a dead switch port. Treat the 169.254 address as a diagnostic flag pointing upstream, not as a setting to delete.