CloudLabBox
Try the free demo

MikroTik MTCIPv6E lab 2 of 8

DHCPv6 prefix delegation from ISP to customer router

Fernvale's ISP network hands each business customer a /56 by DHCPv6 prefix delegation. Build the ISP's pool and DHCPv6 server, make a customer router request a prefix over a WAN link that has only link-local addresses, carve /64s for two LANs from the delegated pool, and let the PCs on both configure themselves.

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 02 - DHCPv6 prefix delegation from ISP to customer router

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
4 vCPU, 1,536 MB
Smallest plan
Lite

The scenario

Fernvale's ISP division delegates a /56 to every business customer, so each customer can number up to 256 LANs itself. The customer router, CPE, has only link-local addresses on its WAN link: it doesn't need a global address there. Build both ends, then give the customer's office LAN and guest LAN a /64 each from the delegated prefix.

DeviceInterfaceIPv6
ISPether1 (to CPE)link-local only; DHCPv6 server delegating /56s from 2001:db8:4800::/40
ISPinternet2001:db8:ffff::1/128 (stands for the Internet)
CPEether1 (WAN)link-local only; DHCPv6 client
CPEether2 (office) · ether3 (guest)the first and second /64 of the delegated /56
PC1 · PC2 (Linux)eth0SLAAC

What you’ll practise

  • Explain stateless and stateful address configuration and where DHCPv6 prefix delegation fits
  • Create an IPv6 pool and a DHCPv6 server that delegates /56 prefixes
  • Request a prefix with the DHCPv6 client and install a default route from it
  • Assign LAN /64s from the delegated pool and advertise them for SLAAC
  • Read bindings, dynamic pools and the routes that delegation creates

The tasks

  1. Start the Linux PCs
  2. Stateless, stateful and delegated
  3. The ISP's pool and DHCPv6 server
  4. The customer router asks for a prefix
  5. Number the LANs from the delegated prefix
  6. The PCs

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 DHCPv6 prefix delegation from ISP to customer router4 nodes, 3 links. Every link is listed as text below the diagram.ISPCPEPC1PC2ether1ether1ether2eth0ether3eth0
4 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • ISP ether1 to CPE ether1
  • CPE ether2 to PC1 eth0
  • CPE ether3 to PC2 eth0
Nodes in DHCPv6 prefix delegation from ISP to customer router, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
ISPMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
CPEMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PC1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
PC2Alpine 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 02 - DHCPv6 prefix delegation from ISP to customer router 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.