CloudLabBox
Try the free demo

MikroTik MTCNA lab 3 of 19

Connect an office to the Internet

Build the classic small-office set-up by hand: a DHCP client on the WAN, a LAN bridge with a DHCP server, the router as DNS cache, and NAT masquerade so the office PCs reach the Internet.

Run this lab

It needs Lite: its 4 nodes are set to 4 vCPU and 2,560 MB in total. That fits the free demo too.

In your workspace: Shared, then MikroTik MTCNA RouterOS v7 guided labs, then 03 - Connect an office to the Internet

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Beginner
Time
About 50 minutes
Nodes need
4 vCPU, 2,560 MB
Smallest plan
Lite

The scenario

Fernvale Networks has connected a florist's shop to its broadband service. The provider's equipment (ISP) hands out a public address with DHCP on the access link. The shop's router (GW) is fresh: it has a name and a password, nothing else. Two PCs are plugged into the shop switch.

Build the set-up that RouterOS's own default configuration gives a home router, by hand, so you understand every part of it: WAN by DHCP, a LAN bridge, DHCP and DNS for the PCs, and NAT.

DeviceInterfaceAddressConnects to
ISPether1203.0.113.1/24, DHCP serverGW ether1
ISPinternet (loopback)198.51.100.10/32, www.fernvale.example–
GWether1 (WAN)DHCP client, 203.0.113.x/24ISP
GWbridge-lan (ether2, ether3)192.168.88.1/24Office LAN
PC1, PC2eth0DHCP from GW (192.168.88.10–254)Office LAN

What you’ll practise

  • Get a WAN address, default route and DNS servers from the provider with a DHCP client
  • Build a LAN bridge, address it and serve DHCP to the office
  • Let the router answer DNS for the LAN
  • Explain why private addresses need source NAT, and add masquerade
  • Use WAN and LAN interface lists the way RouterOS's default configuration does
  • Follow one connection through connection tracking and NAT

The tasks

  1. Get the WAN address from the provider
  2. Build the LAN bridge
  3. Serve DHCP to the office
  4. Make the router the office's DNS server
  5. Reach the Internet with masquerade
  6. Use interface lists, like the default configuration
  7. Watch NAT at 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.

Topology of Connect an office to the Internet4 nodes and 1 network, 4 links. Every link is listed as text below the diagram.ISPGWPC1PC2Office-LANether2eth0eth0ether1ether1
4 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • ISP ether1 to GW ether1
  • GW ether2 to Office-LAN (network)
  • PC1 eth0 to Office-LAN (network)
  • PC2 eth0 to Office-LAN (network)
Nodes in Connect an office to the Internet, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
ISPMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
GWMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC2VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder MikroTik MTCNA RouterOS v7 guided labs.

  3. Open 03 - Connect an office to the Internet and 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

All 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.