MikroTik site onboarding checklist

Use this on site visits so nothing is missed. For how each step works, see Devices and Field notes: common onboarding issues.

1. Pre-Onboarding (Before Site Work)

• Confirm your ISPMan account is created and approved.
• Confirm MikroTik is accessible via WinBox/WebFig/SSH.
• Confirm device identity (model, serial, RouterOS version).
• Confirm required package details (speed, hotspot or PPPoE plan).
• Confirm required equipment is available (MikroTik, ONT, cables, power).

2. Physical and Link Check

• Confirm MikroTik powers on normally.
• Confirm WAN cable from ISP/ONT is connected to intended WAN port.
• Confirm LAN ports/AP uplink are connected correctly.
• Confirm ONT/fiber indicators are healthy (PON/LOS as expected).
• Check for damaged ports, adapters, or cables.

3. WAN Setup on MikroTik

• Open MikroTik and confirm correct WAN method (PPPoE, DHCP, or Static).
• If PPPoE is required, set username/password and enable interface.
• If DHCP is required, confirm DHCP client is active on WAN interface only.
• Confirm WAN receives valid IP/gateway.
• Confirm WAN is not accidentally added to LAN bridge.

4. LAN, Bridge, and DHCP Setup

• Confirm LAN bridge exists and includes intended LAN ports.
• Confirm LAN IP address is configured on the correct bridge/interface.
• Confirm DHCP server is enabled on LAN bridge.
• Confirm DHCP lease assignment from IP > DHCP Server > Leases.
• Confirm NAT masquerade exists with out-interface set to WAN.

5. ISPMan Onboarding Steps

• Add the router under Devices in your ISPMan dashboard.
• Choose onboarding type based on customer scenario:

5.1 Normal Onboarding (Quick Path)

• Download the generated onboarding script from the device page.
• Upload script file to MikroTik (Files).
• Import script from terminal.
• Confirm import completes without errors.
• Confirm device appears online in ISPMan dashboard.

5.2 Manual Onboarding (Controlled Path)

• On the device page, choose More → Start Manual Onboarding.
• Apply the scripts in the order shown on the page.
• Before import, confirm device mode allows script actions.
• Import the final script and click Complete Manual Onboarding on the device page.
• Confirm device appears online in ISPMan dashboard.

6. Service Configuration (Hotspot or PPPoE)

• Hotspot: confirm hotspot server interface is correct and old one is disabled.
• PPPoE: confirm PPPoE server/profile is correct and old one is disabled.
• Confirm the RADIUS settings match the values ISPMan set up.
• Confirm only required active Radius and WireGuard entries remain enabled.
• Confirm the ISPMan user is enabled in System > Users.

7. Validation Tests

• Confirm WireGuard peer shows recent handshake.
• Ping test from MikroTik to public IP (for example 8.8.8.8).
• DNS resolution test from MikroTik.
• Customer-side browsing test (non-HTTPS redirect test if hotspot captive portal is used).
• Speed test and latency test on wired first, then wireless.

8. Handover and Sign-Off

• Confirm customer can connect and access internet.
• Share WiFi credentials (if applicable) and basic reboot guidance.
• Share your support contact and escalation process with the site owner.
• Record final notes (configured interfaces, WAN type, package, date).
• Get sign-off from the site owner.

Bandwidth test from the router

To measure the uplink from the MikroTik itself, run RouterOS’s bandwidth test against a btest server you control:

:local TARGET "<BTEST_SERVER_IP_OR_DOMAIN>"
:local USER "<BTEST_USERNAME>"
:local PASS "<BTEST_PASSWORD>"
/tool/bandwidth-test address=$TARGET user=$USER password=$PASS protocol=tcp direction=both duration=30s

Run it on a wired path first; results well below the line speed point to the uplink, cabling or router CPU rather than WiFi. See also FastTrack if customers go over their package speed.