MikroTik MTCTCE lab 1 of 8
Packet flow, connection tracking and mangle marks
Before Fernvale's Riverside office can shape anything, its router has to recognise the traffic. Trace real packets through the RouterOS packet flow with counting rules, read the connection-tracking table, classify web, bulk and ping traffic with connection and packet marks, and set DSCP so the next hop knows what the traffic is.
Run this lab
It needs Lite: its 3 nodes are set to 3 vCPU and 768 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCTCE RouterOS v7 guided labs, then 01 - Packet flow connection tracking and mangle marks
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 3 vCPU, 768 MB
- Smallest plan
- Lite
The scenario
Fernvale's Riverside office router will soon shape traffic by type: web browsing, bulk transfers and small interactive packets. Shaping by type needs marks, and marks need you to know where in the router a packet is when a rule sees it. In this lab you trace packets through the RouterOS packet flow, read the connection-tracking table, and build the marks that later labs use.
| Device | Address | Role |
|---|---|---|
| NET | 192.0.2.1/30 | the Internet: a web server (WebFig on port 80) and a bandwidth-test server |
| RIVERSIDE | ether1 192.0.2.2/30 · ether2 192.168.50.1/24 | the office router |
| PC1 | 192.168.50.11/24 | a RouterOS router playing a staff PC |
What you’ll practise
- Name the chains a packet passes through when it goes to, through and from the router
- Prove the path with passthrough counter rules
- Read connection states and timeouts in the connection-tracking table
- Mark connections once, then mark their packets cheaply, and explain passthrough
- Change DSCP at the edge and see it at the next router
The tasks
- Put counters in every chain
- Trace three pings
- Read the connection-tracking table
- Mark connections, then packets
- Tell the next hop with DSCP
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
- NET
ether1to RIVERSIDEether1 - RIVERSIDE
ether2to PC1ether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| NET | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| RIVERSIDE | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| PC1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
MikroTik MTCTCE RouterOS v7 guided labs.Open
01 - Packet flow connection tracking and mangle marksand 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 MTCTCE 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.