BryanNet

Multiple routers and locations

Prerequisites and authority

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

Manage several routers and locations

Example: two locations, three routers at each location, one central BryanNet installation. Register all six routers individually with unique identities and reachable management addresses. Group them by meaningful location names.

Monitor three dimensions separately:

Dimension Meaning
Health/reachability Whether management communication succeeds now
Configuration state Whether managed resources match intended configuration
Operations Whether provisioning/sync jobs succeeded for specific targets

A healthy router can have configuration drift. A correct configuration can belong to an unreachable router. An operation may fail on one router while succeeding on the others.

Review location-level summaries, then individual failures. Do not apply a broad reset to six routers because one has a stale account. Keep internet-source failure separate from BryanNet server failure.

For managed MikroTik routers, the persisted hotspot identity is replicated across routers and admission counts customer-wide sessions and pending reservations. Location grouping does not make the entitlement router-specific. Use Cross-router access roaming and accounting to validate the actual topology, personalized hotspot packages and accounting before enabling customer access. Simulated providers retain home-router behavior and are not physical-router acceptance evidence.

Add capacity deliberately: configure routing, onboard the router, reconcile authorized accounts and test access before directing customers to it. Removing a router requires a service handover and preserved historical evidence, not just deleting a dashboard row.

Related guides

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