Networking: IPv6

Networking · Last updated · About 4 min read

Why It Was Needed

IPv4's 32-bit address space tops out around 4.3 billion unique addresses, which is far too small for a world with billions of internet users plus tens of billions of connected devices (smartphones, IoT sensors, and increasingly, IP-connected radio infrastructure). IPv6 solves this with a vastly larger 128-bit address space — roughly 340 undecillion (3.4×10³⁸) unique addresses, for all practical purposes inexhaustible.

Address Format

An IPv6 address is written as eight groups of four hexadecimal digits, separated by colons (e.g. 2001:0db8:0000:0000:0000:ff00:0042:8329), rather than IPv4's four decimal octets. Two shorthand rules make these more manageable: leading zeros in each group can be dropped (0db8 → db8), and one run of consecutive all-zero groups can be collapsed to a double colon :: (the address above becomes 2001:db8::ff00:42:8329) — :: can only be used once per address, since using it twice would make the number of collapsed zero-groups ambiguous.

Address Types

Unlike IPv4, where a given address is just "an address," IPv6 addresses carry meaning by their prefix:

  • Global unicast — the IPv6 equivalent of a public, internet-routable IPv4 address.
  • Link-local (fe80::/10) — automatically self-assigned on every interface, valid only on the local network segment (never routed), and used for essential local operations like neighbor discovery below — every IPv6 interface has one of these regardless of what other addresses it's also configured with.
  • Multicast — IPv6 has no broadcast address at all; anything IPv4 would do with a broadcast (like DHCP's initial Discover step, or ARP resolution) IPv6 does with multicast instead, sent to a specific, narrowly-scoped multicast group rather than to every device on the segment. See Unicast, Broadcast, and Multicast for the general concept.

Neighbor Discovery Protocol (NDP) Replaces ARP

IPv4 uses ARP (Address Resolution Protocol) — a broadcast — to find the MAC address behind an IP address on the local segment. IPv6 replaces this entirely with NDP (Neighbor Discovery Protocol, RFC 4861), which runs over ICMPv6 and uses link-local and multicast addressing instead of a broadcast. NDP also handles SLAAC (Stateless Address Autoconfiguration) — a device can construct its own valid global address from Router Advertisement messages sent by the local router, without needing a DHCP-style server to hand it one — though a network can still run DHCPv6 instead of (or alongside) SLAAC where centralized address tracking/assignment is preferred over pure self-configuration.

Practical Differences from IPv4

Beyond the larger address space, IPv6 removes the need for Network Address Translation (NAT), which IPv4 networks commonly rely on to stretch a limited pool of public addresses across many devices — NAT adds processing overhead and complicates some kinds of direct device-to-device connectivity. IPv6 also supports the built-in auto-configuration described above, and has mandatory support for IPsec, the encryption suite behind many VPNs, where IPv4 only supports IPsec as an optional add-on.

Dual-stack is the common transition strategy: a device or network runs IPv4 and IPv6 side by side simultaneously (rather than an abrupt cutover), letting it reach IPv4-only and IPv6-only destinations alike while the wider migration continues.

Common Misunderstandings

  • "IPv6 means no firewall/security is needed" — removing NAT's side effect of hiding internal addresses is not the same as removing the need for a firewall; every device with a global unicast IPv6 address is potentially directly reachable, which if anything makes an explicit firewall policy more important, not less.
  • "A network claiming 'IPv6 support' definitely uses it for everything" — dual-stack networks frequently run IPv6 "available but idle," with the vast majority of real traffic (and legacy equipment) still riding IPv4; "supports IPv6" and "IPv6 is what's actually carrying this traffic" are different claims.
  • "Link-local addresses are just a lesser/temporary address" — they're a required, permanent part of how every IPv6 interface operates (NDP depends on them), not a fallback or a sign of misconfiguration.

Adoption Status in IT Generally, and in LMR Specifically

IPv6 adoption has grown steadily but gradually — from roughly 1% of Google's traffic in 2012 to over 45% today — meaning most networks, including most LMR/radio-system IP infrastructure, still run IPv4 either exclusively or in a dual-stack configuration alongside IPv6. In land mobile radio specifically, most radio and repeater/base-station equipment in the field today is IPv4-only. Interestingly, the DMR standard's data protocol (TS 102 361-3, see DMR (Digital Mobile Radio)) explicitly describes DMR's packet-data capability as able to carry both IPv4 and IPv6 traffic as a data-bearing subnet over the air interface — a case where the standard itself accommodates IPv6, even though most deployed equipment and site networks in practice are still IPv4. Don't assume IPv6 capability at the protocol-specification level means IPv6 is actually configured or in use on a given deployed system — verify against the specific equipment and site network in question.

References

This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.

Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.