CloudLabBox
Try the free demo

MikroTik MTCIPv6E lab 7 of 8

Routing IPv6: OSPFv3 over link-local links and BGP to an upstream

Fernvale's Harbourside core runs IPv6 on transit links that have no global addresses at all. Bring up OSPFv3 between three routers over link-local addresses, advertise loopbacks and the office LAN, announce Fernvale's /48 to an upstream with eBGP for IPv6, and pass the upstream's default route into OSPFv3 so an office PC reaches the Internet.

Run this lab

It needs Lite: its 5 nodes are set to 5 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 07 - Routing IPv6 - OSPFv3 over link-local links and BGP to an upstream

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
Advanced
Time
About 75 minutes
Nodes need
5 vCPU, 1,536 MB
Smallest plan
Lite

The scenario

Fernvale's Harbourside core is three routers in a row, R1–R2–R3. Its transit links carry IPv6 with no global addresses: only link-local. R1 serves the office LAN; R3 connects to the upstream provider Westlink (AS 64510). Fernvale is AS 64500 and owns 2001:db8:4800::/48. Make it all route.

RouterLoopbackLinks
R12001:db8:4800:ff::1/128ether1 office LAN 2001:db8:4800:10::1/64 · ether2 to R2 (link-local only)
R22001:db8:4800:ff::2/128ether1 to R1, ether2 to R3 (link-local only)
R32001:db8:4800:ff::3/128ether1 to R2 (link-local only) · ether2 2001:db8:e::2/64 to UPSTREAM
UPSTREAMInternet 2001:db8:ffff::1ether1 2001:db8:e::1/64; already configured for BGP

What you’ll practise

  • Explain why IPv6 routing protocols use link-local next hops
  • Configure OSPFv3 in the RouterOS 7 instance, area and interface-template model
  • Read OSPFv3 neighbours, LSAs and routes with link-local gateways
  • Run eBGP for IPv6 with address-families=ipv6 and announce an aggregate from an address list
  • Originate a default route into OSPFv3 from a BGP-learned default

The tasks

  1. Why link-local is enough
  2. OSPFv3 in the core
  3. eBGP for IPv6 to the upstream
  4. A default route for the core

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 Routing IPv6 - OSPFv3 over link-local links and BGP to an upstream5 nodes, 4 links. Every link is listed as text below the diagram.R1R2R3UPSTREAMPC1ether1eth0ether2ether1ether2ether1ether2ether1
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 ether2 to R2 ether1
  • R2 ether2 to R3 ether1
  • R3 ether2 to UPSTREAM ether1
  • R1 ether1 to PC1 eth0
Nodes in Routing IPv6: OSPFv3 over link-local links and BGP to an upstream, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
R2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
R3MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
UPSTREAMMikroTik 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 07 - Routing IPv6 - OSPFv3 over link-local links and BGP to an upstream 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.