MikroTik MTCNA lab 4 of 19
DHCP server in depth and ARP
Run a working DHCP server like a professional: read and manage leases, hand out extra options, reserve an address for a printer, and use ARP reply-only so only devices that got their address from DHCP can use the network.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 2,816 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCNA RouterOS v7 guided labs, then 04 - DHCP server in depth and ARP
- Level
- Intermediate
- Time
- About 50 minutes
- Nodes need
- 4 vCPU, 2,816 MB
- Smallest plan
- Lite
The scenario
An accountancy office runs on the router from lab 3: one subnet, a DHCP server, two PCs and a network printer. Two things go wrong every week. The printer gets a new address after every power cut, so everyone's print jobs fail. And a visitor once plugged in a laptop with a hand-typed address that clashed with the server. The partners want the printer on a fixed address and only DHCP-registered devices on the LAN.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| GW | bridge-lan (ether2) | 192.168.88.1/24, DHCP server dhcp-lan | Office LAN |
| PC1 | eth0 | DHCP | Office LAN |
| PC2 | eth0 | DHCP, later a hand-typed 192.168.88.99 | Office LAN |
| Printer | eth0 | DHCP, reserved 192.168.88.5; MAC 02:00:00:00:88:05 (on its label) | Office LAN |
What you’ll practise
- Read the lease table and explain lease states
- Add domain, NTP and custom options to a DHCP network
- Create a static lease (reservation) for a device by MAC address
- Read the ARP table and explain dynamic, complete and DHCP-added entries
- Use add-arp and arp=reply-only to lock the LAN to DHCP clients
The tasks
- Read the lease table
- Hand out more options
- Reserve an address for the printer
- Read the ARP table
- Only DHCP clients may use the LAN
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
ether2to Office-LAN (network) - PC1
eth0to Office-LAN (network) - PC2
eth0to Office-LAN (network) - Printer
eth0to Office-LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| GW | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| Printer | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 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
04 - DHCP server in depth and ARPand 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.