MikroTik MTCSE lab 3 of 10
RAW table and flood mitigation: SYN, UDP, ICMP and spoofed traffic
An attacker on the ISP segment hammers Fernvale Harbourside's published web server with bursts of TCP SYNs, pings and spoofed packets. Stop them in the RAW table, before connection tracking spends memory on them: per-source SYN and ICMP rate limits that put offenders on a block list, drops for spoofed and broadcast-directed traffic, SYN cookies and strict reverse-path filtering, while a normal visitor keeps loading the site.
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 MTCSE RouterOS v7 guided labs, then 03 - RAW table and flood mitigation - SYN UDP ICMP and spoofed traffic
- Level
- Advanced
- Time
- About 70 minutes
- Nodes need
- 4 vCPU, 1,280 MB
- Smallest plan
- Lite
The scenario
Fernvale Harbourside's router, GW, already has the stateful firewall from lab 2 and publishes the web server WEB on 203.0.113.2 port 80. Now someone on the ISP segment, ATT, is attacking it: bursts of new TCP connections (a SYN flood in miniature), ping bursts, probes of the router's UDP services, pings to the LAN's broadcast address, and packets with a forged private source address. WESTLINK is the ISP's router and also plays a normal visitor who must keep reaching the site.
| Device | Address | Role |
|---|---|---|
| GW | WAN 203.0.113.2/29 · LAN 192.168.40.1/24 · DMZ 172.16.40.1/24 | Fernvale's router |
| WEB | 172.16.40.10/24 | web server, published as 203.0.113.2:80 |
| WESTLINK | 203.0.113.1/29 | the ISP and a normal visitor |
| ATT (Linux) | 203.0.113.6/29, and a forged 10.66.66.66 | the attacker |
What you’ll practise
- Explain why RAW runs before connection tracking and what that costs and saves
- Rate-limit SYNs and echo requests per source with dst-limit, and block offenders dynamically
- Stop smurf amplification and spoofed private sources at the edge
- Turn on SYN cookies and strict reverse-path filtering
- Prove each rule with counters while a legitimate client keeps working
The tasks
- Prepare the attacker
- Why the RAW table
- A per-source SYN limit with dynamic blocking
- ICMP and UDP
- Smurf and spoofing
- Attack, and watch the counters
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
- GW
ether1to WAN (network) - WESTLINK
ether1to WAN (network) - ATT
eth0to WAN (network) - GW
ether3to WEBether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| GW | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| WESTLINK | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| ATT | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| WEB | 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 MTCSE RouterOS v7 guided labs.Open
03 - RAW table and flood mitigation - SYN UDP ICMP and spoofed trafficand 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 MTCSE 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.