Campus and Wi-Fi networks
Design RA and DHCPv6 for large wireless segments, including DNS configuration options. Reduce multicast and ND load on Wi-Fi (RFC 7772). Evaluate a unique IPv6 prefix per host or client (RFC 8273, RFC 9663).
Take the quiz · pass mark 70% · 9 questions
Explanation
Wi-Fi is where IPv6's multicast-based Neighbor Discovery meets a medium that handles multicast badly. Large campus and guest networks need deliberate design or they suffer ND storms and battery drain.
RA, DHCPv6 and DNS on wireless
Hosts learn the prefix and gateway from Router Advertisements. For DNS you can either run DHCPv6 (stateful or stateless, RFC 9915) or advertise DNS directly in the RA using the RDNSS/DNSSL options (RFC 8106) — important because some hosts historically did not do DHCPv6, so RA-based DNS avoids a class of "IPv6 but no resolver" failures. Decide per platform mix; on modern networks advertising DNS in the RA plus DHCPv6 where needed is robust.
Reducing multicast and ND load (RFC 7772)
RA and ND traffic is multicast, and on Wi-Fi multicast is sent at a low basic rate and wakes every device, costing airtime and battery. RFC 7772 (Reducing Energy Consumption of RAs) gives the levers: send unicast RAs in reply to Router Solicitations where possible, keep the RA interval sensible (not too frequent), limit options, and avoid needlessly large or frequent multicast. Access points often add multicast-to-unicast conversion, proxy ND / ND suppression, and client isolation to cut the broadcast domain's ND chatter.
A unique prefix per host (RFC 8273, RFC 9663)
A powerful campus/Wi-Fi design is to give each client its own /64 instead of sharing one /64 across the whole SSID. RFC 8273 describes the unique-IPv6-prefix-per-host model and RFC 9663 defines using DHCPv6-PD (RFC 9915) to allocate a prefix per client. Benefits: each client is alone in its /64, so ND between clients disappears (no shared neighbor cache to attack or flood, better first-hop security, L5.03), the client can even subnet (tethering), and accounting is per-prefix. The cost is more prefixes to delegate and PD support in the infrastructure.
ictNetworks scenario
ictNetworks' campus Wi-Fi advertises DNS in the RA (RFC 8106) alongside DHCPv6 (RFC 9915), tunes RAs per RFC 7772 (unicast RAs to solicitations, sane intervals) and enables multicast-to-unicast and ND suppression on the APs. Its high-security SSID gives each client its own /64 via DHCPv6-PD (RFC 8273/9663), eliminating inter-client ND and shrinking the first-hop attack surface, while the guest SSID keeps a shared /64 with client isolation.
Drawing diagram…
Worked examples
Example 1: Host prefixes from a pool
An AP delegated a /60 to hand out unique per-host /64s can serve 2^(64-60) = 16 clients each with their own /64 before it needs a larger pool.
Example 2: Why unique-prefix-per-host cuts ND
When each client is alone in its own /64, the number of other clients sharing that /64 is 0, so there is no inter-client Neighbor Discovery and no shared neighbor cache to flood or spoof (RFC 8273).
Example 3: Sizing a bigger pool
A /56 per-AP pool supports 2^(64-56) = 256 unique per-host /64s, enough for a dense AP, which is why PD pools are sized at /56 or shorter on busy campus APs.
Lab
Goal: Give each client its own /64 with DHCPv6-PD and compare ND and multicast load with a shared /64.
You need: a namespace/containerlab topology with a router/AP running Kea (DHCPv6 + PD) and radvd, several clients, and a traffic/multicast counter (tcpdump, interface stats). (Kea/radvd syntax varies by version — check the docs.)
- Build a shared /64 SSID: all clients on one /64 with RA + DHCPv6; generate ND traffic and measure the multicast/ND load.
- Tune RAs per RFC 7772 (unicast RAs, interval) and enable multicast-to-unicast/ND suppression; measure the reduction.
- Build a unique-/64-per-host SSID with DHCPv6-PD (RFC 8273/9663); confirm each client gets its own /64.
- Compare inter-client ND and multicast load between the shared and per-host designs.
- Advertise DNS via RA (RFC 8106) and confirm resolution without DHCPv6 on a host that does not use it.
What to submit: the Kea/radvd configuration, the before/after ND-and-multicast measurements, the per-host /64 evidence, and the shared-vs-unique comparison.
Summary
- Wi-Fi handles multicast poorly; RA/ND load matters for airtime and battery (RFC 7772).
- Reduce it with unicast RAs, sane intervals, and AP multicast-to-unicast/ND suppression.
- Advertise DNS in the RA (RFC 8106) and/or run DHCPv6 (RFC 9915) depending on the platform mix.
- A unique /64 per host (RFC 8273, RFC 9663 via DHCPv6-PD) removes inter-client ND and shrinks the attack surface.
- Next lesson (L7.05): data-centre networking.
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.