BryanNet

Prepare a MikroTik for BryanNet

Prerequisites and authority

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

Prepare an existing MikroTik

Use this path when the router already carries a working network. Preserve its configuration before introducing BryanNet. Do not reset an operational router or rebuild its hotspot merely because it is new to BryanNet.

  1. Record RouterOS version, hardware, interfaces and management address.
  2. Export/back up the current RouterOS configuration securely using the supported router tools.
  3. Identify WAN, customer-facing ports/bridges, address pools, DHCP, DNS, NAT and existing hotspot services.
  4. Identify any custom scripts, scheduler entries or profiles that BryanNet may manage.
  5. Establish a dedicated API account and restricted access using RouterOS API access, account policy and firewall hardening.
  6. Confirm reachability from the BryanNet runtime.
  7. Review the shipped Desired State against the existing network before applying it.

Applying a desired configuration may reconcile values that an operator changed manually. Preserve unrelated working services and identify conflicts before the change window. A configuration export is useful evidence but does not guarantee an automatic reverse operation.

For a new router, use New MikroTik configuration using WinBox. BryanNet's supported Desired State can create the managed hotspot components; the new-router journey should not require an unnecessary full manual hotspot wizard first.

The exact policy rights, compatible versions and managed resources must match the selected release. Use Add and bootstrap a router in BryanNet for onboarding and verify actual login before accepting the router.

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.