MikroTik MTCIPv6E lab 3 of 8
Neighbour discovery: RA tuning, router preference, DAD and MLD
Harbourside's office LAN has two routers and hosts that configure themselves, so everything depends on neighbour discovery. Capture router advertisements with tcpdump and tune them: interval, lifetimes, MTU, hop limit, DNS, the M and O flags and router preference. Then watch duplicate address detection fail on purpose, read neighbour states, turn on temporary addresses, and let the bridge snoop MLD.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 1,536 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCIPv6E RouterOS v7 guided labs, then 03 - Neighbour discovery - RA tuning router preference DAD and MLD
- Level
- Advanced
- Time
- About 70 minutes
- Nodes need
- 4 vCPU, 1,536 MB
- Smallest plan
- Lite
The scenario
The Harbourside office LAN (2001:db8:4800:10::/64) has a main router, R1, which also acts as the office switch (its ports ether1–ether3 are bridged as lan), and a backup router, R2. The PCs configure themselves with SLAAC, so neighbour discovery decides which router they use, what MTU and hop limit they use, and where they find DNS. Look at it on the wire, then tune it.
| Device | Address |
|---|---|
| R1 | bridge lan: 2001:db8:4800:10::1/64, advertised |
| R2 | ether1: 2001:db8:4800:10::2/64, also advertised |
| PC1 · PC2 (Linux) | SLAAC |
What you’ll practise
- Name the five ND messages and what each one does
- Tune RouterOS router advertisements and read them on the wire
- Use router preference to make one router the default and another the backup
- See duplicate address detection, neighbour unreachability detection and temporary addresses on a host
- Explain MLD and enable MLD snooping with a querier on a RouterOS bridge
The tasks
- The five messages
- Capture an RA
- Tune R1's advertisements
- A backup router with low preference
- Duplicate address detection and neighbour states
- Temporary addresses
- MLD snooping
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
ether1to PC1eth0 - R1
ether2to PC2eth0 - R1
ether3to R2ether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| R2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| PC1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| PC2 | 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
MikroTik MTCIPv6E RouterOS v7 guided labs.Open
03 - Neighbour discovery - RA tuning router preference DAD and MLDand 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 MikroTik MTCIPv6E labs
Related labs in other courses
CloudLabBox is independent of MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.