MikroTik Router Basic Configuration Step by Step - From Zero to HERO

Summary of the video content (MikroTik Router basic configuration)

This tutorial walks through configuring a MikroTik router “from zero to hero” using WinBox (instead of the web browser). It focuses on step-by-step setup of management access, admin/security, LAN + DHCP, WAN connection with NAT/masquerade, time synchronization via NTP, optional bridging of ports into the LAN, and verification/testing commands.

---

1) Manage the router via WinBox (discovery + login)

• Use WinBox to connect to MikroTik.
• In Neighbors, WinBox auto-detects MikroTik devices on the same network.
• You can connect even without knowing the router IPs (via MAC address discovery).
• Default browser IP mentioned: 192.168.1.1 (web access depends on model/port; WinBox discovery is more convenient).

WinBox device info

• Identity (hostname)
• Version (RouterOS firmware version; example: 7.6)
• Board / CPU architecture
• Uptime

Login defaults and features

• Default username: admin
• Default password: blank (varies by model—often shown on a sticker)
• WinBox options enabled by default:
  • Keep Password
  • Auto reconnect
  • Optional: open in new tab for multiple devices

Initial RouterOS quick config

• After connecting, a default configuration popup appears.
• The tutorial proceeds, then focuses on changing the password.

---

2) Change admin security posture (create a new admin user)

It’s strongly recommended to not use the default admin account.

Steps

1. Go to System → Users
2. Create a new administrator user (example username: Jack)
3. Grant full read/write permissions
4. Set and confirm a password
5. Remove/delete the original admin user after creating the new admin account

Verification

• Reconnect using the new admin credentials.

---

3) Basic identity/host configuration

• Go to System → Identity
• Change hostname (the tutorial shows the title bar updating accordingly).

---

4) Configure LAN interface (example Port 2)

Interface naming

• Go to Interfaces
• Edit Port 2, rename it as LAN
• Confirm status:
  • R = running
  • RX/TX = received/transmitted traffic

LAN IP

• Go to IP → Addresses
• Add an address (example): 10.1.1.254/24
• Assign it to the LAN interface (Port 2)

---

5) Configure DHCP server for LAN

• Go to IP → DHCP Server → DHCP Setup
• Configure on Port 2 / LAN interface

Key settings

• DHCP network address: auto/derived
• DHCP gateway: 10.1.1.254
• DHCP address pool example:
  • From 10.1.1.1 to 10.1.1.200
  • (The subtitle mentions an upper bound like “10.1.1.20000”; intent is a configurable range)
• DNS:
  • Primary: Google DNS
  • Secondary: Cloudflare DNS
  • (If no local DNS is available)
• Lease time:
  • Change from default 10 minutes to 1 day

Verification

• On a connected PC, run:
  • ipconfig /all
• Confirm:
  • IP came via DHCP
  • Default gateway = 10.1.1.254
  • DNS servers were assigned
• Connectivity test:
  • ping the gateway

---

6) Configure WAN interface (example Port 1)

• Configure Port 1 as WAN
• Go to IP → DHCP Client
• Enable DHCP client on Port 1
• Choose Add default route = yes (adds the default route using the ISP router)

Behavior notes (from subtitles)

• Interface status is stopped/red until the cable is connected
• Then it changes to bound/black

Verification

• Go to IP → Routes
• Confirm:
  • Default route destination: 0.0.0.0/0
  • Gateway = ISP router IP
  • Distance shown as 1

---

7) Enable internet access using NAT (masquerade / SNAT)

• Go to IP → Firewall → NAT
• Add rule:
  • Action = masquerade
  • Chain = srcnat
  • Source Network = internal/LAN side

Result

• A network icon indicates internet access

Test internet

• Ping Google DNS and/or google.com

---

8) Set date/time using NTP (for troubleshooting/log accuracy)

• Go to System → Clock
  • Initially may show year 1970 and timezone unset
• Enable NTP client:
  • Mode: unicast
  • Server: pool.ntp.org (optionally add asia.ntp.org)
• Wait until synchronization shows synchronized
• Set timezone:
  • Example: Malaysia UTC+8

Notes

• Auto-sync persists across restarts when configured correctly
• If sync is slow: disable then enable NTP client to refresh

---

9) Optional: Bridge unused ports into the LAN (ports 2–5)

Goal: Make multiple physical ports behave like a single LAN (like a switch).

Bridge setup

1. Create a Bridge interface:
   • Go to Bridge
   • Add a new bridge interface (example: LANbridge)
2. Add ports to the bridge:
   • Add Port 2 (running/master port)
   • Copy binding quickly to add Ports 3, 4, 5
   • Status indicators show:
     • S/slave vs RS (master vs slave)

Rebind LAN IP + DHCP

• Change LAN IP interface from Port 2 to LANbridge
• Update DHCP server interface to LANbridge
  • Fixes error: “DHCP server cannot run on slave interface”

Verification

• Devices plugged into ports 2–5 stay on the same network
• Internet test: ping Google

---

10) Optional: Configure WAN static addressing (instead of DHCP)

Steps

• Remove the DHCP client on WAN (Port 1)
• Remove auto default route (it disappears when DHCP client is removed)
• Add a WAN static IP address:
  • Must be in the same subnet as the ISP router
  • Ensure the IP is not already used
• Add default route manually:
  • 0.0.0.0/0 with gateway = ISP router IP

Verification

• Ping google.com

---

Main speakers/sources

• Main speaker: “deoro” (narrator/author introduced as “deoro today…”)
• Software/role sources: WinBox and MikroTik RouterOS (example version: 7.6)
• External services referenced:
  • Google DNS
  • Cloudflare DNS
  • pool.ntp.org
  • asia.ntp.org