BryanNet

Shipped Desired State presets and safe customization

Prerequisites and authority

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

Use shipped Desired State as the supported baseline

Desired State describes the router configuration BryanNet intends to manage. It can reconcile drift, which means manual RouterOS edits may be replaced when the relevant managed component is applied again.

The owner-approved support boundary is the shipped preset configuration for the matching release. Operator-customized presets require independent testing; BryanNet cannot promise identical behavior after arbitrary changes.

  1. Confirm the preset version and intended topology.
  2. Compare interfaces, bridge, management/customer addressing and upstream assumptions.
  3. Preserve the current router configuration and a recovery access path.
  4. Review inspection/differences if the released interface exposes them.
  5. Apply through the authorized workflow during an appropriate window.
  6. Inspect per-component results, then test management and customer access.

The inspected service contains handlers for interfaces, bridge, IP address/pool, DHCP, hotspot profile/server, DNS, NAT and address lists. That inventory is not a published preset schema or a guarantee that every key is accepted.

Do not paste arbitrary JSON examples into production. Desired State preset reference records the schema/publication contract. If customization is needed, test it on an isolated router with representative login, quota, concurrency and recovery behavior.

Undoing a configuration change is not necessarily one atomic rollback. Keep router export/backups and document the manual recovery path. Stop if management access is lost or the change affects unrelated services.

Related guides

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