Systems and protocols · Intermediate

IPv6: addresses, neighbors and path MTU

Understand prefix notation, neighbor discovery and why IPv6 changes troubleshooting assumptions.

Ask Logeia about this articleTry the three questionsReview your answers

Updated

On this page
  1. Read the address
  2. Find a neighbor
  3. Routers do not fragment IPv6 packets
  4. Check both protocol families
  5. Ask Logeia about this articleCheck your understanding

Read the address

IPv6 uses 128-bit addresses written as colon-separated hexadecimal groups. A double colon abbreviates a run of zero groups and can appear only once in one address, so expansion stays unambiguous. A suffix such as /64 is the prefix length, not a port or packet size.

One interface can hold several addresses with different purposes and scopes. A link-local destination may require an interface identifier to distinguish the link being addressed. Copying only the visible address can therefore omit information needed by a diagnostic command.

Find a neighbor

IPv6 neighbor discovery uses ICMPv6 rather than the IPv4 ARP procedure. It supports functions including learning link-layer neighbors and discovering routers. A configured address is not sufficient if the endpoint cannot resolve the neighbor needed for its next hop.

A firewall rule copied from an IPv4 deployment can accidentally block essential IPv6 control traffic. Do not classify all ICMPv6 as an optional ping feature. Decide which message types the network requires, and verify their behavior on both the local link and the routed path.

Routers do not fragment IPv6 packets

IPv6 routers do not fragment transit packets in the IPv4 manner. Fragmentation, where needed, is performed by the source using a fragment header. Information such as a Packet Too Big message is therefore important for selecting a workable packet size along a path.

If a tiny request succeeds but a larger response stalls, investigate path MTU and blocked control messages as well as application errors. Comparing controlled packet sizes can help locate the boundary. A successful small ping is insufficient to rule out a size-dependent failure.

Check both protocol families

With both A and AAAA records, the chosen address family can affect the result. IPv4 and IPv6 have different routes, firewall rules and listener configurations. Success on one family does not establish the health of the other. Record which address and family a failed attempt actually used.

IPv6 does not automatically encrypt application traffic, and the absence of NAT does not imply unrestricted inbound reachability. TLS, access control and routing remain separate responsibilities. Test each family deliberately before attributing an intermittent failure to random application behavior.

Reading and practice are recorded separately in this browser, for each language.

Learn this in order

Understand the systems behind the web · STEP 9

Choose a learning path