What you'll need
- WinBox or FTP access to each RouterOS router you're connecting
- MikroTik does not have a cloud controller — this is a self-hosted, per-router setup. There's no fleet-wide config push; each router needs the steps below done individually.
- The MyWiFi RADIUS server IP and shared secret from your MyWiFi device registration screen
Steps
- In the MyWiFi dashboard, go to Devices and click Add Device. Select the Location, name the device, and under Select Your Hardware choose MikroTik Routerboard. Note the NASID value MyWiFi assigns to this device — you'll need it below. Because MikroTik has no cloud controller, this step just registers the router and generates your RADIUS credentials; there's no controller URL or API key to enter.
- On the router, configure the RADIUS client with the address, secret, and ports MyWiFi gave you:
`` /radius add service=hotspot address={MyWiFi RADIUS IP} secret={shared secret} authentication-port=1812 accounting-port=1813 /ip hotspot profile set {profile-name} use-radius=yes radius-accounting=yes radius-interim-update=2m ``
- Upload the custom
rlogin.htmltemplate MyWiFi provides to the router's/hotspotdirectory, using the WinBox Files panel or FTP. This file redirects guests to your MyWiFi portal along with the session details the router needs to complete login. - Add MyWiFi's portal IP or domain to the router's Walled Garden so guests can reach the splash page before they've logged in:
`` /ip hotspot walled-garden ip add dst-address={MyWiFi portal IP} action=accept ``
- Set the hotspot profile's login method to allow CHAP and MAC-based login:
`` /ip hotspot profile set {profile-name} login-by=http-chap,mac ``
Best practice: Because there's no cloud controller for MikroTik, every router in a multi-site deployment needs its own
rlogin.htmlupload and RADIUS configuration. Budget time per router rather than expecting a one-time, fleet-wide setup — and keep a checklist so no router in a rollout gets missed.
Comments
Please sign in to leave a comment.