CloudLabBox
Try the free demo

MikroTik MTCIPv6E lab 5 of 8

Transition: 6in4, DS-Lite by hand with IPIPv6, GRE6 and EoIPv6

Not every Fernvale site has both protocols. Give an IPv4-only branch IPv6 through a 6in4 tunnel, give an IPv6-only customer IPv4 through a DS-Lite softwire you build from an IPIPv6 tunnel and NAT44, and join two IPv6 sites at layer 3 with GRE6 and at layer 2 with EoIPv6, then watch the MTU shrink with every tunnel.

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 05 - Transition - 6in4 DS-Lite by hand with IPIPv6 GRE6 and EoIPv6

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

The scenario

Fernvale runs a dual-stack core, but two kinds of site don't:

  • the BR4 branch still has an IPv4-only uplink and wants IPv6;
  • a new access network is IPv6-only, and its customers (router B4, with a PC that speaks only IPv4) still need to reach IPv4 hosts such as BR4.

CORE plays the tunnel broker for the first and the AFTR for the second.

DeviceInterfaceAddress
COREether1 · ether2 · internet203.0.113.1/30 · 2001:db8:a::1/64 · 198.18.0.1/24 and 2001:db8:ffff::1
BR4ether1203.0.113.2/30 (IPv4 only)
B4ether1 · ether22001:db8:a::2/64 (IPv6 only) · 192.168.1.1/24
PC (Linux)eth0192.168.1.10/24

What you’ll practise

  • Compare dual stack, 6to4, 6in4, 6RD, Teredo and DS-Lite
  • Build a 6in4 tunnel to carry IPv6 over an IPv4-only network
  • Build DS-Lite's B4 and AFTR from an IPIPv6 tunnel and a NAT44 rule
  • Use GRE6 and EoIPv6 over an IPv6 network
  • Explain why tunnels lower the MTU and how IPv6 handles fragmentation

The tasks

  1. Address the PC
  2. The transition toolbox
  3. 6in4 for the IPv4-only branch
  4. DS-Lite: the softwire
  5. DS-Lite: the AFTR's NAT
  6. Layer 3 and layer 2 over IPv6: GRE6 and EoIPv6
  7. MTU and fragmentation

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 Transition - 6in4 DS-Lite by hand with IPIPv6 GRE6 and EoIPv64 nodes, 3 links. Every link is listed as text below the diagram.COREBR4B4PCether2eth0ether1ether1ether2ether1
4 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • CORE ether1 to BR4 ether1
  • CORE ether2 to B4 ether1
  • B4 ether2 to PC eth0
Nodes in Transition: 6in4, DS-Lite by hand with IPIPv6, GRE6 and EoIPv6, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
COREMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
BR4MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
B4MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PCAlpine 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 05 - Transition - 6in4 DS-Lite by hand with IPIPv6 GRE6 and EoIPv6 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.