Important: Back up the router first. If it is already serving customers, arrange a maintenance window or ask a MikroTik technician to help.
What you need before you start
- A MikroTik router running a supported RouterOS release.
- An internet connection from Starlink, fibre, fixed wireless, or another ISP.
- An access point, or a MikroTik model with wireless built in.
- A laptop with WinBox or access to WebFig.
- A plan for package times, speeds, data allowances, and prices in GHS.
Update RouterOS, replace the default administrator credentials, and export a configuration backup before changing the network.
Choose a simple network layout
Keep the internet-facing port outside the guest bridge. Put the LAN ports and access points used by guests inside one dedicated bridge. MikroTik’s documentation recommends running the HotSpot server on the bridge interface itself, not on an individual bridge port.
Set up the HotSpot in RouterOS
- Connect the WAN. Give the internet-facing interface a DHCP client or the static details provided by the ISP. Confirm that the router can reach the internet.
- Create the guest bridge. Add the LAN and wireless interfaces that should carry guest traffic. Do not add the public WAN interface.
- Add the guest IP and DHCP server. Choose a private subnet, create an address pool that excludes the router’s own address, and run DHCP Setup on the guest bridge.
- Run HotSpot Setup. In WinBox or WebFig, open IP → Hotspot, choose Hotspot Setup, and select the guest bridge. RouterOS creates the required HotSpot settings for you.
- Set the DNS name carefully. A proper hotspot DNS name and valid certificate improve captive-portal detection on modern phones. Avoid using a name that points somewhere else on the public internet.
- Create one test user. Under IP → Hotspot → Users, add a temporary username and password, then test before connecting billing.
The official MikroTik HotSpot documentation recommends the setup wizard because it adds the required settings and explains how the captive portal works.
Create packages with sensible limits
Use HotSpot user profiles for reusable speed rules, then attach each sold user to the correct profile. Apply time or data limits to the user that Corbin Point creates.
| Package | Suggested control | Good for |
|---|---|---|
| 1 hour | Limit uptime and moderate speed | Visitors and quick access |
| 1 day | 24-hour access with a fair speed cap | Short-stay guests |
| 1 week | Speed tier plus optional data allowance | Hostel residents |
| 1 month | Defined profile and clear fair-use policy | Long-term customers |
RouterOS supports limit-uptime, total byte limits, and user profiles. Start conservatively, observe peak-hour performance, and adjust packages using real usage rather than guesswork.
Test the customer journey
- Forget the Wi-Fi network on a phone, reconnect, and wait for the sign-in prompt.
- If no prompt appears, open a plain HTTP page to trigger redirection.
- Log in with the test user and confirm browsing works.
- Check the active user in RouterOS and confirm time and data counters move.
- Confirm the user disconnects when the purchased limit is reached.
Test Android and iPhone devices separately. Modern captive-portal detection works best when the HotSpot DNS name and certificate are correctly configured.
Connect the router to Corbin Point
Once the manual test user works, add the router from the Corbin Point admin dashboard. Use the secure connector rather than exposing RouterOS management ports directly to the public internet. Then match each Corbin Point package to the correct MikroTik profile.
Common mistakes to avoid
- Putting the WAN port inside the hotspot bridge.
- Using the same subnet on both sides of the router.
- Publishing WinBox or RouterOS API ports openly on the internet.
- Creating “unlimited” plans without a speed policy or capacity check.
- Skipping an end-to-end test after changing a profile.
Ready to manage the hotspot?