Connect your access point to Wibizpro and start selling WiFi access in minutes.
In RouterOS, open New Terminal and paste this block as is:
# 1. RADIUS — this site's own secret /radius add address=144.202.47.181 secret=rad_xxx service=hotspot \ authentication-port=1812 accounting-port=1813 # 2. DNS — two settings that are NOT the same thing. # a) The router must answer its CLIENTS. Without this the portal # never appears: the hotspot works by intercepting DNS. /ip dns set allow-remote-requests=yes # b) The router's OWN upstream resolver. 8.8.8.8 is fine HERE — it is # the router asking, not the clients. A factory router already # learns one from the ISP; this line just makes it explicit. /ip dns set servers=8.8.8.8,1.1.1.1 # 3. Address pool for the clients /ip pool add name=wibizpro-pool ranges=192.168.88.10-192.168.88.254 # 4. Hotspot profile /ip hotspot profile add name=wibizpro hotspot-address=192.168.88.1 \ dns-name=wifi.local use-radius=yes radius-accounting=yes \ radius-interim-update=1m login-by=mac,http-pap # 5. Hotspot, on the bridge the access points are wired to /ip hotspot add name=wibizpro interface=bridge \ address-pool=wibizpro-pool profile=wibizpro disabled=no # 6. THE CAPTIVE LOGIN PAGE — this is where your Portal URL goes. # Without this step the client sees the ROUTER's own login page and # your portal never appears. Run it after step 5 (the hotspot # creates the file). # $(mac-esc) is filled in by the router for each client — leave it # exactly as written, backslash included. /file set [find name~"login.html"] contents="<html><body><script>window.location.href='https://wipay.online/portal/?token=dt_your-site-token&clientMac=\$(mac-esc)'</script></body></html>"wibizpro and wibizpro-pool are just names. Any name works, as long as it is the same everywhere in the block.192.168.88.x is MikroTik's factory LAN. If your network uses another range, change all four addresses — the pool, the hotspot address, and both profile references.bridge is the interface the hotspot runs on — the one your access points are wired to. If yours has another name, use it there.8.8.8.8 is fine there. What matters is that the clients ask the router, never a public resolver directly. Never hand 8.8.8.8 to the clients.login.html so the client is sent to your page instead of RouterOS's own login. If the command refuses to run — some firmware versions object to the quotes — do it by hand instead: in Winbox, Files → the hotspot folder → open login.html and replace its whole contents with this (keep $(mac-esc) exactly as written — the router fills it in):
<html><body><script>window.location.href='https://wipay.online/portal/?token=dt_your-site-token&clientMac=$(mac-esc)'</script></body></html>
Replace rad_xxx with your site's secret. The hotspot lives on the router — never on the access points.
The captive login page, the WireGuard tunnel and the CoA operations are covered in the full runbook: docs/mikrotik-site-setup.md
Unpaid clients are blocked until they authenticate — including the Wibizpro page itself. Allow it in the walled garden:
/ip hotspot walled-garden add dst-host=wibizpro.online action=allow add dst-host=*.wibizpro.online action=allow /ip hotspot walled-garden ip add action=accept dst-host=wibizpro.online add action=accept dst-address=144.202.47.181Also allow your payment providers' domains, and Apple's captive-portal endpoints (17.0.0.0/8 and *captive.apple.com) — without those, iPhones never show the login page.
Any brand works — the access points are transparent bridges. On each one:
Once configured, here is what your customers experience:
Expired clients are automatically disconnected at the exact end of their pass.
You can monetize several networks differently — all from a single Wibizpro dashboard:
Example:
| SSID | Portal URL | Pricing |
|---|---|---|
| GuestWiFi | /portal/?token=dt_guest |
$1–$25 USD |
| Premium | /portal/?token=dt_prem |
$5–$100 USD |
| Staff | No portal | Free |
The SSIDs can share the same hardware — no extra equipment needed. Revenue from each is tracked separately in your Wibizpro dashboard.
Standalone TP-Link Omada access points are still supported. If you already have one running, this is its configuration — it does not change.
On the Wireless → Portal tab of your EAP (e.g. EAP110), fill in exactly these values:
In the Wireless → Portal tab, open the Free Authentication Policy and add:
Each entry needs a name — e.g. Wibizpro-80, Wibizpro-443, DNS.
Enter each address in the Destination field, and its port in Destination Port — never in Source. The policy is a list of places clients are ALLOWED to reach before paying, so the address belongs on the destination side.
Better still: keep the access point and put a MikroTik router in front of it as the gateway. Your EAP110 keeps working — set it to bridge mode, turn off its captive portal and its RADIUS, and follow the five steps above instead.
Wibizpro hosts the captive portal for you. We handle:
Your Wibizpro dashboard gives you full visibility: