MikroTik Hotspot Setup for a Small ISP — A Step-by-Step Guide
Planning a small ISP or society WiFi network? A practical MikroTik hotspot guide: hardware, RouterOS setup, user profiles, speed limits and mistakes to avoid.
Across small towns in Gujarat and the rest of India, local ISPs and WiFi operators are serving societies, hostels, hotels and villages where big providers do not bother laying fibre. The tool of choice for most of them is MikroTik — affordable routers with carrier-grade software. The built-in Hotspot feature lets you give each customer a username and password, control their speed, and track usage. This guide walks through a practical setup for a small operator handling 50 to 500 users.
Step 1: Choose the right hardware
Do not start with the cheapest board and do not overbuy either. Rough sizing for hotspot use:
- Up to 50 users: hEX (RB750Gr3) — around Rs 5,500, handles 100-plus Mbps of hotspot traffic comfortably.
- 50 to 200 users: RB4011 or L009 — more CPU cores for queues and PPPoE/Hotspot processing.
- 200 to 1000 users: CCR series (for example CCR2004) — a proper multi-core router built for this job.
Add a UPS — power cuts corrupt configurations and anger customers — and use decent outdoor CPE (LiteBeam, Cube, or similar) for wireless distribution. The router is the brain; do not make it fight cheap cabling and crimping. Use good CAT6 and proper earthing, especially during Gujarat's monsoon lightning season.
Step 2: RouterOS basics before anything else
Connect via Winbox (the Windows configuration tool) to the router's MAC address. Before touching the hotspot, do the hygiene work:
- Update RouterOS to the latest stable version (System > Packages).
- Set a strong admin password and create a second admin user as backup.
- Set the correct time zone and enable NTP so logs make sense.
- Configure WAN on ether1 (DHCP client or static IP from your upstream provider) and confirm the router itself can ping 8.8.8.8.
- Disable unused services (System > Users and IP > Services): telnet, ftp, and restrict Winbox access to your management IP if possible.
Step 3: Create the hotspot server
MikroTik makes the basic setup almost automatic:
- Decide your LAN interface (say ether2, or a bridge of ether2-ether5 plus WLAN).
- Give it an IP such as 10.5.50.1/24.
- Go to IP > Hotspot > Hotspot Setup and follow the wizard: select the interface, accept the address pool (for example 10.5.50.2-10.5.50.254), skip the SSL certificate for now, use 8.8.8.8 as DNS, set a DNS name like wifi.local, and create the first test user.
That is it — any device connecting to that interface now gets redirected to a login page. Test immediately with a phone: connect, see the login portal, sign in with the test user, browse. If redirection fails, check that the hotspot interface has a DHCP server and that your device actually received a 10.5.50.x address.
Step 4: User profiles and bandwidth limits
Profiles are where you define your actual plans. Under IP > Hotspot > User Profiles, create one profile per package:
- Basic-10M: Rate Limit 10M/10M, Shared Users 1, session timeout as per plan.
- Family-25M: Rate Limit 25M/25M, Shared Users 3 so one login works on three devices.
- Hotel-Guest: Rate Limit 5M/5M with a 24-hour validity.
The Rate Limit field follows the format upload/download (for example 5M/10M). For fair usage during peak evening hours, look into burst settings (for example 12M burst on a 10M plan for the first 30 seconds) — customers feel speed where it matters, page loads and app opens. Then create users under IP > Hotspot > Users and assign each to a profile. For prepaid vouchers, generate batches of random username/password pairs with limited uptime.
Common mistakes that kill small ISPs
- No backups. Export your configuration (/export file=backup) after every change and store it off the router.
- One flat network. Separate management, hotspot users and CCTV/office devices with VLANs or at least separate bridges.
- Selling speed you do not have. Fifty users on 25M plans need honest upstream capacity and contention planning, not hope.
- Ignoring bypasses. Bind known devices by MAC only where justified (printers, STBs), and watch for MAC spoofing.
- Default DNS open to the world — close remote DNS requests or your router becomes part of DDoS attacks.
- Doing accounting in a notebook. Expiry dates, payments and complaints on paper collapse beyond 40-50 customers.
When a management panel makes sense
RouterOS is excellent at networking but was never meant to be your billing office. Once you cross roughly 50 paying customers, you will spend hours every month creating users, disabling expired ones, and answering "recharge karva nu che" calls. A management panel that talks to the router via the API automates this: customer signup, plan renewal, online payment, automatic disconnection on expiry, usage reports and WhatsApp payment reminders. That is exactly the layer Krishna WiFi provides on top of MikroTik for small ISPs and hotspot operators — the router keeps doing what it does best, and the panel handles the business side. Start with the manual setup above to learn the fundamentals; add the panel when the notebook stops scaling.
Final advice
Build slowly and document everything: IP plan, tower locations, customer MACs, upstream details. A small ISP wins on service, not speed claims — when the network drops during a storm and you restore it in twenty minutes because your configuration was clean and backed up, customers stay for years.