CloudLabBox
Try the free demo

MikroTik MTCRE lab 4 of 14

Point-to-point addressing

Save address space the way ISPs do: link routers with /32 point-to-point addresses instead of /30s, serve several customers from one provider address, and route a customer's public block over those links.

Run this lab

It needs Lite: its 5 nodes are set to 5 vCPU and 2,048 MB in total. That fits the free demo too.

In your workspace: Shared, then MikroTik MTCRE RouterOS v7 guided labs, then 04 - Point-to-point addressing

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 45 minutes
Nodes need
5 vCPU, 2,048 MB
Smallest plan
Lite

The scenario

Fernvale is running out of public IPv4 space. Every customer link today burns a /30 (four addresses for two routers) and every core link the same. The new standard: core links use /32 point-to-point addresses, and the access router PE uses one single address towards every customer, so each customer costs exactly one address. You'll build it for the core link and two business customers, one of which (C1) has a routed public block.

LinkPE sideFar side
PE ether1 ↔ Core ether110.255.0.1/32, network 10.255.0.210.255.0.2/32, network 10.255.0.1
PE ether2 ↔ C1 ether1100.64.0.1/32, network 100.64.0.2100.64.0.2/32, network 100.64.0.1
PE ether3 ↔ C2 ether1100.64.0.1/32, network 100.64.0.3100.64.0.3/32, network 100.64.0.1
C1 ether2–203.0.113.1/28 (PC1 .10)
Core internet–198.51.100.10 (test host)

What you’ll practise

  • Explain how a /32 address with a network= peer works on Ethernet
  • Address a core link with point-to-point /32s
  • Reuse one provider address on several customer links
  • Route through point-to-point next hops
  • Compare with /30 subnets and with PPP's dynamic point-to-point addresses

The tasks

  1. Understand point-to-point addresses
  2. Address the core link
  3. One provider address for every customer
  4. Route across the point-to-point links
  5. Compare the address cost

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 Point-to-point addressing5 nodes, 4 links. Every link is listed as text below the diagram.CorePEC1C2PC1ether2eth0ether1ether1ether2ether1ether3ether1
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • Core ether1 to PE ether1
  • PE ether2 to C1 ether1
  • PE ether3 to C2 ether1
  • C1 ether2 to PC1 eth0
Nodes in Point-to-point addressing, 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
PEMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
C1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
C2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 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 MTCRE RouterOS v7 guided labs.

  3. Open 04 - Point-to-point addressing 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 MTCRE labs

All MikroTik MTCRE labs

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.