MikroTik MTCNA lab 10 of 19
Firewall: protect the customers, address lists and FastTrack
Protect the networks behind the router: prove that NAT is not a firewall, build the forward chain the way RouterOS's default configuration does, keep guests away from staff, block sites with an address list, and see what FastTrack does.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 3,072 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCNA RouterOS v7 guided labs, then 10 - Firewall - protect the customers address lists and FastTrack
- Level
- Intermediate
- Time
- About 55 minutes
- Nodes need
- 5 vCPU, 3,072 MB
- Smallest plan
- Lite
The scenario
A guest house runs staff PCs and free guest Wi-Fi from one MikroTik. Its input chain (from lab 9) is in place, so the router itself is safe, but there are no forward rules. Fernvale's security team has put a route on the provider side pointing at the staff LAN, to show what an attacker on the provider network could do. The owners also want guests kept away from the staff PCs, and two websites blocked for staff.
| Device | Interface | Address |
|---|---|---|
| GW | ether1 (WAN) · ether2 (Staff) · ether3 (Guest) | 203.0.113.2/30 · 192.168.10.1/24 · 192.168.20.1/24 |
| ISP | ether1 · ether2 · sites loopback | 203.0.113.1/30 · 198.51.100.1/24 · 192.0.2.10, .66, .77 |
| Remote | eth0 | 198.51.100.10/24 (attacker's host) |
| Staff-PC · Guest-PC | eth0 | 192.168.10.10 · 192.168.20.10 |
What you’ll practise
- Show that masquerade alone doesn't stop inbound connections
- Build a forward chain: FastTrack, accept established, drop invalid, drop new connections from WAN that aren't DST-NATed
- Isolate one LAN from another with interface matchers
- Block destinations with a static and a timed address-list entry, and choose between drop and reject
- Explain FastTrack, its counters and what it bypasses
The tasks
- Prepare Remote
- Prove that NAT is not a firewall
- Build the forward chain
- Keep guests away from staff
- Block sites with an address list
- Watch FastTrack work
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
- ISP
ether1to GWether1 - ISP
ether2to Remoteeth0 - GW
ether2to Staff-PCeth0 - GW
ether3to Guest-PCeth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| ISP | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| GW | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| Remote | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| Staff-PC | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| Guest-PC | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
MikroTik MTCNA RouterOS v7 guided labs.Open
10 - Firewall - protect the customers address lists and FastTrackand 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 MTCNA 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.