BryanNet

Cross-router access roaming and accounting

Prerequisites and authority

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

Verify cross-router access

Managed MikroTik routers use the customer's persisted hotspot identity across routers and locations without requiring a router-specific subscription. Customer-wide admissions count live sessions and unexpired reservations. The local regression tests exercise provisioning, reject-new concurrency and accounting behavior using isolated fixtures; they do not certify physical firmware, wireless handover or a customer's network. Run the following topology checks before enabling access on a new site.

Provision the correct account/profile to all applicable routers. Aggregate usage against the active subscription and enforce its concurrency across the combined session set. A customer changing devices or sites should not create duplicate entitlements.

The same persisted hotspot identity is replicated across every managed MikroTik router in this installation; assigned home-router metadata remains and simulated providers retain home-router behavior. Rebuild and redeploy personalized hotspot packages on each router. Stale packages without routing identity are rejected in multi-router installations. Routing tokens select the actual admission router and are not management credentials. A signing-key change requires hotspot redeployment, not subscriber credential migration. Replica failures stay pending; unowned username collisions are not overwritten. Review pending state before retrying and retain a recovery path.

Run this controlled test:

  1. Create one customer and one active test subscription.
  2. Authenticate on router A, disconnect, then authenticate on router B.
  3. Repeat across two locations and verify credentials/profile.
  4. Connect on A and B simultaneously up to the permitted limit.
  5. Attempt one more session at capacity and verify reject-new behavior while established connections remain intact. Count unexpired pending reservations as well as live sessions across every managed MikroTik router.
  6. Compare combined usage with the subscription allowance.
  7. Exhaust quota or reach expiry and verify the next queued plan activates correctly.
  8. Repeat with one management path temporarily unavailable, then reconcile.

Application logout, wireless roaming between access points and cross-router entitlement roaming are distinct. This guide does not promise seamless radio handover or zero interruption during authentication.

Record router/session IDs, ordering and timestamps. Test credentials existing on only one router as a negative case. Do not mark roaming complete solely because the customer table lacks a router foreign key.

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.