CloudLabBox
Try the free demo

MikroTik MTCRE practice labs

14 guided labs on RouterOS 7 that cover every module of the MTCRE training outline: static routing with ECMP, check-gateway, recursive next hops and policy routing, point-to-point addressing, PPP and IPsec VPNs, VLANs and QinQ, and OSPF from a single area to stub, NSSA, virtual links and routing filters, plus VRRP and an MPLS preview, ending in a troubleshooting lab and a regional ISP core.

Start this courseTry it free for 30 minutes

Standard for a month, £75.00, runs every lab here, with nothing extra to pay for the guided labs. 13 of the 14 labs also run in the free demo.

Guided labs
14
Follows
MikroTik MTCRE, on RouterOS v7
Runs every lab
Standard
Devices
RouterOS and VPCS

Who these labs are for

For engineers who hold or are working towards the MTCNA and are preparing for the MTCRE course and exam, and anyone who runs routed MikroTik networks at an ISP or a multi-site business.

The labs use the RouterOS 7 routing menus, which differ from version 6.

The 14 labs

Every lab in the folder, as the workspace lists them, with what each runs and the smallest plan that fits. Read on 2 November 2026.

MTCRE course 14 labs

Shared folderMikroTik MTCRE RouterOS v7 guided labs

One MTCRE module per lab, then a troubleshooting lab and a regional ISP core capstone.

  1. 01Static routing in depth - specific routes ECMP check-gateway and distance

    Engineer traffic across two parallel paths with nothing but static routes: steer one subnet with a more specific route, balance with ECMP, force a gateway through a named interface, detect dead next hops with check-gateway, keep a floating backup, and stop routing loops with a blackhole aggregate.

    4× RouterOS, 2× VPCS

    6 vCPU, 3,072 MBFits LiteRuns in the free demo

  2. 02Recursive next hops scope and dual-ISP fail-over

    Build dual-ISP fail-over that notices an outage beyond the provider's first router: pin a probe host to each provider, make the default routes recursive through those hosts with scope and target-scope, check them with ping, and stop the probes leaking through the other provider.

    4× RouterOS, 1× VPCS

    5 vCPU, 2,048 MBFits LiteRuns in the free demo

  3. 03Policy routing with routing tables rules and mangle

    Send different traffic out of different providers: create routing tables, route a whole subnet with a routing rule, steer one application with mangle routing marks, keep local traffic in the main table, and give each policy a fall-back.

    4× RouterOS, 2× VPCS

    6 vCPU, 3,072 MBFits LiteRuns in the free demo

  4. 04Point-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.

    4× RouterOS, 1× VPCS

    5 vCPU, 2,048 MBFits LiteRuns in the free demo

  5. 05PPP VPNs - L2TP over IPsec and SSTP between sites

    Join a branch to head office with the PPP-based VPNs of the MTCRE outline: L2TP protected by IPsec as the main tunnel and SSTP over TLS with your own certificate authority as the backup, with routes pushed from the PPP secrets and automatic fall-back.

    3× RouterOS, 2× VPCS

    5 vCPU, 2,816 MBFits LiteRuns in the free demo

  6. 06VLANs and QinQ across a provider network

    Carry a customer's own VLANs between two sites across Fernvale's network without touching them: each provider edge wraps everything the customer sends in an 802.1ad service tag (S-VLAN 100), using an S-VLAN interface bridged to the customer port.

    4× RouterOS, 2× VPCS

    6 vCPU, 3,072 MBFits LiteRuns in the free demo

  7. 07Single-area OSPF on RouterOS 7

    Bring up OSPF the RouterOS 7 way (instance, area, interface templates), watch neighbours reach Full and 2-Way, control the DR/BDR election on a shared segment, read the link-state database, and steer traffic with interface costs.

    4× RouterOS, 2× VPCS

    6 vCPU, 3,072 MBFits LiteRuns in the free demo

  8. 08Multi-area OSPF external routes and summarisation

    Split Fernvale's OSPF network into areas: build two area border routers, summarise a branch area with an area range, redistribute customer networks as external type 1 and type 2 routes with a routing filter, and originate a default route from the Internet edge.

    5× RouterOS, 1× VPCS

    6 vCPU, 2,304 MBFits LiteRuns in the free demo

  9. 09Stub totally stubby and NSSA areas and virtual links

    Shrink a branch's routing table with stub and totally stubby areas, then turn the area into an NSSA so the branch can still inject its own external routes, and rescue an area that isn't connected to the backbone with a virtual link.

    5× RouterOS, 1× VPCS

    6 vCPU, 2,304 MBFits LiteRuns in the free demo

  10. 10OSPF routing filters and their limits

    Write RouterOS 7 routing filter rules: control which networks an ASBR exports and with what metric and type, discover why an inbound filter on a link-state protocol creates a black hole, and fix the problem at its source.

    4× RouterOS, 2× VPCS

    6 vCPU, 3,072 MBFits LiteRuns in the free demo

  11. 11VRRP - a gateway that survives a router failure

    Give an office LAN a gateway address shared by two routers with VRRP v3: elect a master by priority, test fail-over and pre-emption, and make the master step down when its own uplink fails, using netwatch.

    3× RouterOS, 2× VPCS

    5 vCPU, 2,816 MBFits LiteRuns in the free demo

  12. 12MPLS LDP and VPLS - MTCINE preview

    Go one step beyond MTCRE: label-switch Fernvale's OSPF core with MPLS and LDP, read label bindings and the forwarding table, then build a VPLS pseudowire that joins two customer sites at layer 2 across the core.

    5× RouterOS

    5 vCPU, 1,280 MBFits LiteRuns in the free demo

  13. 13Troubleshooting a routed network

    A five-router OSPF network after a weekend of changes: the branch PC can't reach the Internet. Walk the path neighbour by neighbour with RouterOS 7's OSPF tools and find five faults: an area mismatch, mismatched timers, a passive transit link, a missing default route and a typo that hides a LAN.

    5× RouterOS, 1× VPCS

    6 vCPU, 2,304 MBFits LiteRuns in the free demo

  14. 14Capstone - a regional ISP core

    Build Fernvale's new core from blank routers: point-to-point addressing, multi-area OSPF with an NSSA at a point of presence, a dual-ISP edge with recursive fail-over that originates the default route, a VRRP gateway pair for customers, and a branch joined by OSPF over a GRE tunnel.

    8× RouterOS, 2× VPCS

    10 vCPU, 4,096 MBFits Standard

Devices and images

The exact Add Node images the labs use, and the vCPU and RAM their nodes are set to. Your plan counts what each running node is set to.

Devices and images in the MikroTik MTCRE practice labs, as read on 2 November 2026
DeviceImage in Add NodeSet toLabsNodes
MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB1462
VPCS hostBuilt in to EVE-NGcounted as 1 vCPU, 1,024 MB1321

Browse every image in the Add Node list

How to open the labs

  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 a lab and start its nodes, then open Lab Tasks for the steps.

The labs are read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change a lab, rebuild it in your own folder.

The Shared folder in the EVE-NG File Manager, recorded on 2 November 2026 with a test account.
The EVE-NG File Manager open on the read-only Shared folder: one folder per guided course, including Arista EOS, BGP in depth, CCIE Enterprise Infrastructure, CCNA, CCNP ENARSI and ENCOR, Check Point, Cisco ASA, Cisco Nexus NX-OS, CompTIA Network Plus and FortiGate
A guided CCNA lab with its Lab Tasks pane, recorded on 1 November 2026 with a test account.
A guided CCNA lab open in EVE-NG with its nodes running: four routers and two PCs on the canvas, and the Lab Tasks pane beside them with the scenario, the addressing plan and the first task

Questions about the MikroTik MTCRE labs

Are these MikroTik MTCRE labs free?

They’re included with every lab plan, with nothing extra to pay, rather than free. Plans start at £3 a day or £0.50 an hour. To try one first, the free demo gives you 30 minutes with 6 vCPU and 8 GB, enough to run 13 of these labs.

Which plan do I need for these labs?

Standard, with 12 vCPU and 16 GB, runs every lab here. Lite runs 13 of the 14. EVE-NG admits a node by the vCPU and RAM configured on it, so a lab needs the total its running nodes are set to. The biggest here, “Capstone - a regional ISP core”, needs 10 vCPU and 4,096 MB. Each lab’s Lab Tasks pane names the plan it needs.

Can I change these labs?

You can start the nodes and configure the devices, but the labs are read-only: changes to the topology can’t be saved. To change one, rebuild it in your own folder.

Are these labs from MikroTik?

No. CloudLabBox wrote them to follow the topics of MikroTik’s MTCRE (MikroTik Certified Routing Engineer) training outline. They aren’t training material from MikroTik, and CloudLabBox is independent of MikroTik.

Try a lab before you choose

The free demo is a real workspace for 30 minutes, with 6 vCPU and 8 GB: enough to run 13 of these labs. No card and no email.

Try it free for 30 minutesStart this course

Plans from £3 a day or £0.50 an hour, each with every guided lab.

More practice labs

CloudLabBox is independent of MikroTik. The labs follow exam topics and aren’t vendor training material; vendor names identify the exams and the images in the workspace.