MikroTik MTCNA lab 2 of 19
Users, services and secure management access
Give each administrator their own account with the right rights, switch off the management services nobody needs, and allow SSH, WinBox and MAC access only from the IT network.
Run this lab
It needs Lite: its 3 nodes are set to 3 vCPU and 1,280 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCNA RouterOS v7 guided labs, then 02 - Users services and secure management access
- Level
- Beginner
- Time
- About 50 minutes
- Nodes need
- 3 vCPU, 1,280 MB
- Smallest plan
- Lite
The scenario
The bakery's router from lab 1 is now in a bigger customer: a vet practice with an IT room and a staff office. Three people at Fernvale log in to it, all as admin, and nobody can tell who changed what. The router also answers Telnet, FTP and the API on every interface, so anyone in the staff office can try to log in.
Your job: named accounts with the right rights, only the management services that are needed, and management only from the IT LAN.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| R1 | ether2 | 192.168.10.1/24 | Admin-PC (IT LAN) |
| R1 | ether3 | 192.168.20.1/24 | Staff-PC (Staff LAN) |
| Admin-PC | eth0 | 192.168.10.10/24, gateway 192.168.10.1 | R1 ether2 |
| Staff-PC | eth0 | 192.168.20.10/24, gateway 192.168.20.1 | R1 ether3 |
| Account | Group | Password |
|---|---|---|
netadmin (Fernvale engineer) | full | Net-admin1 |
support (helpdesk, look but don't touch) | helpdesk (you create it) | Help-desk1 |
What you’ll practise
- Explain RouterOS user groups and policies, and create a read-only helpdesk group
- Create named administrator accounts instead of sharing admin
- List the management services and their ports, and disable the insecure ones
- Restrict SSH and WinBox to a management subnet
- Limit MAC-WinBox, MAC-Telnet and neighbour discovery to a trusted interface list
- Prove the result from an allowed and a non-allowed host
The tasks
- Prepare the two PCs
- See what the router exposes
- Create a read-only helpdesk group
- Create named accounts
- Test the helpdesk account
- Switch off the services nobody needs
- Limit layer-2 access and discovery to the IT port
- Prove it from both offices
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
- R1
ether2to Admin-PCeth0 - R1
ether3to Staff-PCeth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| Admin-PC | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| Staff-PC | 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
02 - Users services and secure management accessand 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.