CloudLabBox
Try the free demo

MikroTik MTCIPv6E lab 1 of 8

IPv6 addressing, address types and SLAAC

Fernvale's Harbourside office gets its first IPv6 addresses from Fernvale's /48. Plan the subnets, read the link-local and EUI-64 addresses RouterOS creates, give the staff LAN a prefix that hosts configure themselves with SLAAC, address a server statically, and see multicast, neighbour discovery and the IPv6 header at work.

Run this lab

It needs Lite: its 3 nodes are set to 3 vCPU and 1,024 MB in total. That fits the free demo too.

In your workspace: Shared, then MikroTik MTCIPv6E RouterOS v7 guided labs, then 01 - IPv6 addressing address types and SLAAC

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 60 minutes
Nodes need
3 vCPU, 1,024 MB
Smallest plan
Lite

The scenario

Fernvale Networks has an IPv6 allocation, and the Harbourside office gets the site prefix 2001:db8:4800::/48 from it (2001:db8::/32 is the documentation prefix; it stands in for Fernvale's real one). Today you bring up IPv6 on the office router GW: a staff LAN whose PCs configure themselves, and a server LAN with a statically addressed server.

DeviceInterfaceIPv6
GWether1 (staff LAN)2001:db8:4800:10::1/64, advertised for SLAAC
GWether2 (server LAN)2001:db8:4800:20::1/64, plus an EUI-64 address
SRVether12001:db8:4800:20::10/64, static
PC1 (Linux)eth0SLAAC from 2001:db8:4800:10::/64

What you’ll practise

  • Write and shorten IPv6 addresses, and explain how prefixes are allocated down to a /64
  • Recognise link-local, global, unique local, multicast and special addresses
  • Derive an EUI-64 interface ID from a MAC address and let RouterOS build one
  • Advertise a /64 so a Linux host configures itself with SLAAC, and route to a static server
  • Name the fields of the IPv6 header and what changed from IPv4

The tasks

  1. Start the Linux PC
  2. Addresses, notation and the plan
  3. Link-local addresses and EUI-64
  4. Global addresses on GW
  5. SLAAC on the staff LAN
  6. A static server and routing
  7. Multicast, neighbours and the header

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.

Topology of IPv6 addressing address types and SLAAC3 nodes, 2 links. Every link is listed as text below the diagram.GWSRVPC1ether1eth0ether2ether1
3 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • GW ether1 to PC1 eth0
  • GW ether2 to SRV ether1
Nodes in IPv6 addressing, address types and SLAAC, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
GWMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
SRVMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PC1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder MikroTik MTCIPv6E RouterOS v7 guided labs.

  3. Open 01 - IPv6 addressing address types and SLAAC and 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

All 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.