MikroTik MTCSE lab 7 of 10
Certificates and PKI: your own CA, HTTPS, SSH keys and SSH tunnels
Fernvale's NOC wants every management session encrypted and verifiable. Build Fernvale's own certificate authority on the Harbourside router, serve WebFig over HTTPS with a certificate that a client can verify, give the NOC engineer a key-only SSH account, and reach a switch's web page on an isolated management network through an SSH tunnel.
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 07 - Certificates and PKI - your own CA HTTPS SSH keys and SSH tunnels
- Level
- Advanced
- Time
- About 70 minutes
- Nodes need
- 4 vCPU, 1,280 MB
- Smallest plan
- Lite
The scenario
Fernvale's NOC wants every management session to be encrypted and verifiable: no clicking through browser warnings, no shared passwords typed into SSH. You'll make the Harbourside router EDGE the home of Fernvale's own certificate authority, serve WebFig over HTTPS with a certificate issued by it, give the NOC engineer an SSH account that accepts only a key, and use SSH to reach a switch whose management network the firewall keeps closed to everyone but EDGE.
| Device | Address | Role |
|---|---|---|
| EDGE | ether1 10.10.10.1/24 (NOC LAN) · ether2 172.16.99.1/24 (switch management) | router and CA |
| SW | 172.16.99.2/24 | a switch's WebFig, forwarding to it is blocked |
| AUD | 10.10.10.30/24 | an auditor's PC (RouterOS) that checks certificates |
| NOC (Linux) | 10.10.10.10/24 | the engineer's workstation |
What you’ll practise
- Explain symmetric and asymmetric cryptography, hashes, signatures and how a PKI uses them
- Create a CA and issue a server certificate on RouterOS, and export the CA certificate
- Serve WebFig over HTTPS and verify it from a client that trusts the CA
- Log in with an SSH key instead of a password
- Forward a local port through SSH to reach a network the firewall otherwise blocks
The tasks
- Address the NOC workstation
- The ideas behind certificates
- Build the CA and a server certificate
- WebFig over HTTPS, verified
- A key-only SSH account for the engineer
- Reach the switch through an SSH tunnel
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
- EDGE
ether1to NOC-LAN (network) - AUD
ether1to NOC-LAN (network) - NOC
eth0to NOC-LAN (network) - EDGE
ether2to SWether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| EDGE | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| SW | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| AUD | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| NOC | 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 MTCSE RouterOS v7 guided labs.Open
07 - Certificates and PKI - your own CA HTTPS SSH keys and SSH tunnelsand 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
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.