IPv6 in practice lab 2 of 12
NDP in depth: RS, RA, NS, NA, DAD and the M and O flags
Replace ARP in your head. Capture every Neighbor Discovery message on a live LAN, watch Duplicate Address Detection stop a clash on Linux and IOS, then change the M, O and A flags and router preference and see hosts react.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 2,048 MB in total. That fits the free demo too.
In your workspace: Shared, then IPv6 in practice across vendors guided labs, then 02 - NDP in depth - RS RA NS NA DAD and the M and O flags
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 4 vCPU, 2,048 MB
- Smallest plan
- Lite
The scenario
The staff LAN at Kestrel Freight now runs IPv6, and the helpdesk keeps being asked why a laptop picks up the "wrong" address. Before anyone changes anything, you spend an hour reading the LAN: every Neighbor Discovery message, every flag. By the end you can explain exactly what each host hears and why it does what it does.
| Device | Interface | Address |
|---|---|---|
| R1 | Gi0/0 | fe80::1, 2001:db8:100:10::1/64, sends RAs every 15 s |
| R2 | Gi0/0 | fe80::2, 2001:db8:100:10::2/64, IPv6 routing off for now |
| H1, H2 | eth0 | SLAAC from R1's RAs |
| Device | Runs | How to log in |
|---|---|---|
| R1, R2 | Cisco IOSv 15.9 | The console opens at >; enable has no password. |
| H1, H2 | Alpine Linux | root, no password. |
What you’ll practise
- Identify RS, RA, NS and NA in a capture and name each one's source and destination
- Work out a solicited-node multicast address and find it on a host and a router
- Show Duplicate Address Detection stopping an address clash on Linux and IOS
- Set the M, O and A flags on IOS and predict what a host does with each
- Use router preference and a zero router lifetime to control which router hosts use
The tasks
- Start the Linux hosts
- Router Solicitation and Router Advertisement
- Neighbor Solicitation and Advertisement
- Duplicate Address Detection
- The M, O and A flags
- Two routers: preference and lifetime
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- R1
Gi0/0to Staff (network) - R2
Gi0/0to Staff (network) - H1
eth0to Staff (network) - H2
eth0to Staff (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| H2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
IPv6 in practice across vendors guided labs.Open
02 - NDP in depth - RS RA NS NA DAD and the M and O flagsand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More IPv6 in practice labs
Related labs in other courses
CloudLabBox is independent of Cisco, CompTIA, Juniper Networks and MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.