BryanNetSupported RouterOS versions, API ports and permissions
Prerequisites and authority
Use this reference with your installed release. Internal implementation routes and settings are not public integration contracts.
RouterOS compatibility and API requirements
Confirm the exact router model, RouterOS version, management interface and intended features with BryanNet before deployment. This guide does not guarantee compatibility with every RouterOS version or device. Test the proposed configuration on a non-production router before changing an existing network.
| Interface | Conventional port | Documentation boundary |
|---|---|---|
| RouterOS API | TCP 8728 | Restricted LAN/VPN management |
| RouterOS API-SSL | TCP 8729 | Not supported by the current connection implementation; do not use as the BryanNet management endpoint |
| WireGuard | Chosen UDP port | Firmware-specific implementation and routes |
The baseline guide creates a dedicated user with read,write,api. Treat that as a starting example, not a certified complete least-privilege group. Required operations can include hotspot users/profiles, sessions, scripts, schedulers, addressing, DHCP and NAT. Validate the chosen rights against all managed functions.
The router record contains a use_ssl field, but the current MikroTik connection passes host, port, credentials and timeout to librouteros.connect without a TLS wrapper or certificate-verification configuration. Setting that field or selecting port 8729 does not implement encrypted API transport. Restrict the existing API to a private management LAN or VPN; do not expose unencrypted router management to the public Internet.
Firmware compatibility is more than TCP connection success. Test authentication, inspection/apply, provisioning, disconnection, event callbacks, accounting and recovery on representative physical hardware.
Keep the API private and restrict permitted sources with the router input firewall. A listed provider option is not a compatibility guarantee. Include the model, firmware version and management topology when requesting deployment confirmation or support.
Related guides
Related guides: Configuration reference (env vars, ports, URLs), Docker services, Compose files and persistent volumes, Database diagnostics and safe query reference, Subscription and provisioning state model.