MikroTik MTCIPv6E lab 6 of 8
PPPoE with IPv6: per-session prefixes and delegation
Fernvale's broadband customers connect with PPPoE. Make the access concentrator dual-stack: an IPv4 address from a pool, a /64 for the PPP link and a /56 delegated over DHCPv6 for every session, all from one PPP profile. Connect two customer routers, number a LAN from the delegated prefix, and see what the concentrator creates for each session.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 1,280 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCIPv6E RouterOS v7 guided labs, then 06 - PPPoE with IPv6 - per-session prefixes and delegation
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 4 vCPU, 1,280 MB
- Smallest plan
- Lite
The scenario
Fernvale's broadband customers connect to the BRAS (broadband remote access server) with PPPoE. Until now they got IPv4 only. Make every session dual-stack from one PPP profile:
- an IPv4 address from 100.64.0.0/24 (shared address space, as carriers use);
- a /64 for the PPP link itself, from 2001:db8:5000::/48;
- a /56 delegated over DHCPv6 for the customer's LANs, from 2001:db8:5100::/40.
| Device | Interface | Notes |
|---|---|---|
| BRAS | ether2 (access network) · internet | PPPoE server; 198.18.0.1 and 2001:db8:ffff::1 stand for the Internet |
| CPE1 | ether1 (PPPoE as cust1) · ether2 (LAN, PC1) | customer router |
| CPE2 | ether1 (PPPoE as cust2) | a second customer |
| PC1 (Linux) | eth0 | SLAAC |
What you’ll practise
- Explain how IPv6 runs over PPP: IPv6CP, link-local identifiers, and DHCPv6 over the session
- Configure a PPP profile with remote-ipv6-prefix-pool and dhcpv6-pd-pool
- Request a delegated prefix over a PPPoE client interface and number a LAN from it
- Read the dynamic DHCPv6 server, bindings and routes RouterOS creates per session
The tasks
- IPv6 over PPP
- Pools and profile on the BRAS
- Connect the customers
- The customer's LAN
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
- BRAS
ether2to Access (network) - CPE1
ether1to Access (network) - CPE2
ether1to Access (network) - CPE1
ether2to PC1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| BRAS | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CPE1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CPE2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| PC1 | 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
06 - PPPoE with IPv6 - per-session prefixes and delegationand 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.