Validate hotspot login, provisioning and router health

Prerequisites and authority

Network/RouterOS authority, known topology and a recovery management path are required. Preserve existing router configuration before managed changes.

Verify a serving hotspot

Router health and usable customer internet are separate acceptance results. Test a dedicated customer on a representative device and access point.

1. Confirm the router's management connection and latest operation outcome.
2. Inspect the managed hotspot server/profile, address pool, DHCP, DNS and NAT appropriate to the topology.
3. Register the test customer through an entitled interface.
4. Purchase or assign a test plan and inspect active/queued state.
5. Confirm provisioning produced the intended enabled account/profile.
6. Join the customer network, obtain an address and open the hotspot login path.
7. Authenticate with hotspot credentials and access an external site.
8. Confirm sessions and usage appear in BryanNet.
9. Test a controlled disconnect, concurrency boundary and expiry/quota event.

Use hotspot credentials, not an assumed website password. A successful manual router login without a BryanNet subscription does not prove provisioning works.

Record customer, subscription and router identifiers, timestamps, firmware and results. Multi-router deployments also require Cross-router access roaming and accounting acceptance.

If internet works but accounting does not, the setup is incomplete. If management works but the customer cannot obtain an IP address, investigate the customer network before changing payment data. Subscription active but no internet access and Hotspot captive portal login issues follow the failure chain.

Related guides

Related guides: RouterOS API access, account policy and firewall hardening, Shipped Desired State presets and safe customization, Internet sources and multi-site network topology, Router connection fails or API authentication is rejected.