BryanNet

Add and bootstrap a router in BryanNet

Prerequisites and authority

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

Add and bootstrap a router

Prepare the router using Prepare a MikroTik for BryanNet or New MikroTik configuration using WinBox. Confirm the management IP/hostname and API port are reachable before opening Router Management → Routers and the supported Add Router flow.

Enter a recognizable name, actual management address, appropriate implemented router provider/type, API port and dedicated credentials. Select the location where offered. A physical-router label in the interface must not be confused with proof that every provider option is implemented.

  1. Save/test the connection through the current workflow.
  2. Review the selected shipped Desired State and managed network resources.
  3. Apply/bootstrap through the supported action.
  4. Inspect its operation result and errors.
  5. Verify router health, managed resources and a real customer connection.

BryanNet generates a router identifier and secret for managed router-to-platform events. These differ from the API username/password used by BryanNet to log into RouterOS. Do not manually invent a secret on the router or expose it in screenshots.

Do not describe an inspection/diff screen as available until the UI has been checked. The source contains inspection and reconciliation machinery; operator-visible controls remain a release check.

If bootstrap partly succeeds, inspect its recorded outcome before retrying. An API connection test does not validate permissions to manage bridges, DHCP, scripts, hotspot resources or NAT. Keep your original configuration and a management recovery path available.

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.