MikroTik Network Administration
A RouterOS administration case study covering interface inventory, bridge/VLAN design, DHCP, firewall policy, NAT, routing, and verification. The emphasis is on making network behavior observable and recoverable.
TOPOLOGY
The lab separates management, user, and server traffic with VLAN-aware switching. A simple addressing plan is documented before configuration so that every interface, subnet, and policy has a defined purpose.
ROUTEROS CONFIGURATION
Configuration is applied in logical layers: interfaces → bridge/VLAN → IP addressing → DHCP/DNS → routes → NAT → firewall. Safe-mode/backup practices are considered before remote changes.
VERIFICATION COMMANDS
RouterOS commands such as /interface print, /ip address print, /ip route print, /ip firewall filter print stats, and /tool torch provide evidence for configuration and traffic behavior.
[admin@lab-router] > /interface print terse 0 R ether1 name="WAN" 1 R ether2 name="LAN-TRUNK" [admin@lab-router] > /ip address print 192.0.2.2/30 interface=WAN 192.168.50.1/24 interface=VLAN50
[admin@lab-router] > /ip route print where dst-address=0.0.0.0/0 DAcS 0.0.0.0/0 gateway=192.0.2.1 [admin@lab-router] > /ip firewall filter print stats 0 ... accept established,related packets=1842 1 ... drop invalid packets=7
INCIDENT SCENARIO
A VLAN client receiving DHCP but failing to reach a server is traced through VLAN tagging, gateway reachability, firewall counters, and routing. Counters are more useful than repeatedly editing rules without evidence.
LESSONS LEARNED
The key operational skill is controlled change. Export configuration before major edits, keep management access independent where possible, and verify each layer before moving to the next.