OSNTC.016: IPv6 Addressing and Neighbor Discovery — Prefixes, SLAAC, NDP, Routing, and Transition

IPv6 networking lesson cover showing a network switch, IPv6 prefix, global unicast, link-local, SLAAC, and neighbor discovery in neon green.

IPv6 expands Internet Protocol addressing from 32 bits to 128 bits and changes several technician workflows at the same time. OSNTC.016 follows OSNTC.015: NAT and PAT Basics by moving from IPv4 address conservation toward globally scalable IPv6 addressing, where technicians must recognize prefixes, address types, autoconfiguration, neighbor discovery, and IPv6 routing behavior.

Professor Messer — IPv6 Addressing, CompTIA Network+ N10-009. Introduces IPv6 addressing and coexistence with IPv4.

Learning objectives

  • Read and shorten IPv6 addresses correctly.
  • Interpret IPv6 prefix lengths such as /64.
  • Distinguish global unicast, link-local, unique-local, multicast, and loopback addresses.
  • Explain SLAAC and DHCPv6 at technician level.
  • Explain how Neighbor Discovery replaces key IPv4 ARP functions.
  • Configure and verify basic IPv6 connectivity.
  • Recognize IPv6 routing and IPv4-to-IPv6 transition methods.

IPv6 notation, hexadecimal, and compression

An IPv6 address contains eight 16-bit hexadecimal groups, for a total of 128 bits. Leading zeros inside a group can be omitted, and one continuous run of all-zero groups can be replaced once with ::; therefore 2001:0db8:0000:0000:0000:0000:0000:0025 can be written as 2001:db8::25. A technician must be able to expand and compress addresses without changing their value.

Intelligence Quest — IPv6 Address Compression Explained. Demonstrates leading-zero removal, double-colon compression, and correct expansion.

Prefixes and the common /64 boundary

An IPv6 prefix length identifies how many leading bits describe the network portion of an address. A typical LAN uses a /64, leaving 64 bits for the interface identifier; for example, 2001:db8:10:20::/64 identifies the subnet while the remaining bits identify interfaces. Prefix length is conceptually similar to an IPv4 subnet mask, but IPv6 technicians normally work directly with CIDR notation instead of dotted-decimal masks.

Pedro Lino Cáceres — IPv6 tutorial for CCNA. Covers IPv6 structure, representation, address types, and practical configuration.

Global, link-local, unique-local, multicast, and loopback addresses

IPv6 technicians should recognize several important address scopes. Global unicast addresses are generally drawn from 2000::/3 and are designed for globally routable communication; link-local addresses use fe80::/10 and operate only on the local Layer 2 link; unique-local space uses fc00::/7; multicast begins with ff00::/8; and the loopback address is ::1. Unlike IPv4, ordinary IPv6 operation does not use broadcast addressing.

Mohamed Herak — IPv6 Addressing: Address Types. Reviews link-local, unique-local, global unicast, and multicast address categories.

SLAAC and DHCPv6

Stateless Address Autoconfiguration allows an IPv6 host to learn network information from Router Advertisement messages and construct an address without relying on an IPv4-style DHCP exchange. DHCPv6 can still provide stateful addressing or additional configuration, depending on the network design. A technician should inspect Router Advertisements, address assignment, prefix information, default-router behavior, and DNS configuration instead of assuming that every IPv6 client receives all settings from DHCP.

OneMarcFifty — IPv6 explained: SLAAC and DHCPv6. Covers Router Solicitation, Router Advertisement, autoconfiguration, and DHCPv6 behavior.

Neighbor Discovery replaces key ARP functions

IPv6 Neighbor Discovery Protocol uses ICMPv6 messages and multicast to perform functions that IPv4 separates across ARP and other mechanisms. Neighbor Solicitation and Neighbor Advertisement messages discover local-link neighbors, while Router Solicitation and Router Advertisement messages help hosts discover routers and prefixes. The neighbor cache is therefore one of the first places to inspect when a host has an IPv6 address but cannot reach a device on the same link.

Wendell Odom’s Network Upskill — Neighbor Discovery Protocol. Explains how IPv6 NDP replaces ARP-style neighbor resolution and uses solicited-node multicast.

Configuration and verification

IPv6 troubleshooting begins by verifying the interface state, assigned global and link-local addresses, prefix length, default route, neighbor cache, and end-to-end ICMPv6 reachability. On Cisco-style devices, useful commands include show ipv6 interface brief, show ipv6 neighbors, show ipv6 route, and IPv6-aware ping; on Linux, technicians can use ip -6 addr, ip -6 route, ip -6 neigh, and ping -6.

NetworkShip — IPv6 Configuration in Cisco Packet Tracer. Demonstrates global and link-local addressing, verification, and IPv6 ping tests.
Cisco-style verification
show ipv6 interface brief
show ipv6 neighbors
show ipv6 route
ping 2001:db8:10:20::25

Linux verification
ip -6 addr
ip -6 route
ip -6 neigh
ping -6 2001:db8:10:20::25

IPv6 routing

IPv6 routers forward traffic by longest-prefix match just as IPv4 routers do, but IPv6 routing tables contain IPv6 prefixes and can use link-local next-hop addresses. Static routes are useful for small or controlled topologies, while dynamic routing protocols such as OSPFv3 can distribute IPv6 reachability in larger networks. When an IPv6 destination fails, technicians should separate local-link neighbor discovery from the routed path and verify each hop in sequence.

Network Direction — IPv6 Routing Explained. Covers static IPv6 routes, link-local next hops, and OSPFv3 concepts.

IPv4 and IPv6 coexistence

Most production environments migrate gradually rather than switching from IPv4 to IPv6 in one event. Dual-stack systems run both protocols, tunneling can carry one protocol across another network, and translation mechanisms such as NAT64 allow IPv6-only clients to reach IPv4-only services under defined conditions. Technicians should identify which transition method is in use before troubleshooting because an IPv6 symptom can originate in native IPv6 routing, DNS64, translation state, or the remaining IPv4 path.

Sunny Classroom — IPv4 to IPv6 Transition with NAT64. Explains coexistence, translation, and IPv6-to-IPv4 connectivity.

Reference standards

Prior lessons

Exercises

  1. Expand 2001:db8:20::45 into all eight hexadecimal groups.
  2. Compress 2001:0db8:0000:0000:0000:00aa:0000:0001 correctly.
  3. Identify the scope or type of fe80::1, ::1, 2001:db8::25, and ff02::1.
  4. Explain why a /64 leaves 64 bits for an interface identifier.
  5. Compare SLAAC with DHCPv6 in two or three sentences.
  6. Map IPv4 ARP terminology to the closest IPv6 Neighbor Discovery behavior.
  7. Use a lab or Packet Tracer topology to verify an IPv6 address, neighbor entry, route, and ping.
  8. Describe one situation where NAT64 would be required.

Knowledge check

  1. How many bits are in an IPv6 address?
  2. How many times can :: appear in one compressed IPv6 address?
  3. What prefix identifies IPv6 link-local addresses?
  4. What protocol family carries Neighbor Solicitation and Router Advertisement messages?
  5. What does SLAAC allow a host to do?
  6. Which command shows IPv6 neighbors on a Cisco-style device?
  7. Can an IPv6 static route use a link-local next hop?
  8. What does NAT64 accomplish?

Answers

  1. 128 bits.
  2. Once.
  3. fe80::/10.
  4. ICMPv6.
  5. Learn prefix/router information and construct an IPv6 address without a stateful address lease.
  6. show ipv6 neighbors.
  7. Yes, when the platform and route syntax identify the appropriate outgoing interface or otherwise disambiguate the next hop.
  8. It translates between IPv6 and IPv4 so compatible IPv6-only and IPv4-only endpoints can communicate through a translation system.

One response to “OSNTC.016: IPv6 Addressing and Neighbor Discovery — Prefixes, SLAAC, NDP, Routing, and Transition”

  1. […] APIs and networked systems often return JSON, but parsing is only the first step: the program still has to verify required […]

    Like

Leave a comment