MikroTik is often the control plane for small ISPs
Many ISPs and WISPs already use MikroTik for queues, PPPoE, DHCP, firewall rules, routing, and subscriber access. ISPAgents should not force those operators to abandon working routers before they can automate operations.
The MikroTik integration connects billing and customer state to controlled RouterOS actions.
What the integration can support
- Suspend unpaid subscribers.
- Restore paid subscribers.
- Change plan speed or shaping policy.
- Apply queue or address-list changes.
- Read router state for support context.
- Record before and after evidence.
- Require approvals for risky changes.
- Show connector health and failures.
Direct control and RADIUS can coexist
Some networks should use RADIUS as the primary access control layer. Others need direct RouterOS actions because of legacy design, private networks, or operator preference.
ISPAgents supports both patterns:
| Pattern | Best for | |---|---| | MikroTik direct control | Simple networks, queue/address-list workflows, quick deployment. | | FreeRADIUS integration | PPPoE or centralized auth networks with existing RADIUS. | | Managed RADIUS | Operators that want cloud-managed auth and less server maintenance. | | Custom connector | Private/NAT networks, vendor-specific logic, or unusual site layouts. |
Safety matters
Router automation must be controlled. ISPAgents should show:
- The customer affected.
- The router and policy affected.
- The command preview.
- The approval state.
- The execution result.
- The rollback or recovery evidence.
FAQ
Can ISPAgents cut off MikroTik users automatically?
Yes. The product can automate suspension and restoration through RouterOS API, RADIUS, or a connector depending on how the ISP network is designed.
Does this require replacing MikroTik?
No. MikroTik remains the router platform. ISPAgents becomes the operations layer that coordinates billing, access state, support context, and audit evidence.