Which MikroTik connection methods does ISPbox support?

ISPbox connects over the RouterOS API (default port 8728) using the router API username and password. For routers behind NAT or without a public IP, you can connect them through an encrypted WireGuard tunnel and manage them over that instead.

Do I need a RADIUS server to use MikroTik with ISPbox?

No. You can run each router in API mode, where ISPbox provisions PPPoE secrets, DHCP leases, and queues directly over the RouterOS API. If you prefer RADIUS, ISPbox registers the router as a NAS and pushes credentials and rate limits through it - both PPPoE and DHCP are supported either way.

How does ISPbox apply subscriber speed limits on MikroTik?

Speed limits come from the customer service package. In API mode ISPbox creates a MikroTik simple queue per client; in RADIUS mode it sends the MikroTik Rate-Limit attribute. When a customer changes plans, the limit updates automatically.

Does ISPbox support both PPPoE and DHCP on MikroTik?

Yes. Each router can run PPPoE (username and password sessions via /ppp/secret and profiles) or DHCP (static leases that bind a MAC to an IP). ISPbox can also run an initial setup that creates the bridge, PPPoE server, profiles, and address pools for you.

Do changes in the panel reach the router automatically?

Yes. Activating, suspending, or cancelling a service writes or removes the matching configuration on the router, so what you bill and what the network enforces stay in sync.

ISPbox

01 Feature Spotlight

MikroTik Integration for Daily ISP Operations

Unify subscriber operations and billing around your MikroTik environment without stitching together separate tools.

Operational workflows aligned with MikroTik deployments
Billing and customer context linked to network execution
Faster troubleshooting with shared platform visibility

Create Free Account View Pricing

app.ispbox.net

→ Under the hood

How ISPbox connects to and provisions MikroTik

ISPbox talks to your MikroTik routers over the native RouterOS API, so a change in the panel becomes real router configuration in seconds - no manual Winbox edits, no pasting scripts by hand. Run PPPoE or DHCP, authenticate over RADIUS or straight through the API, and ISPbox keeps billing, access, and traffic shaping in step with what is actually configured on the router.

Connect over the RouterOS API or a WireGuard tunnel

Add a router with its IP, API username and password, and API port (8728 by default) and ISPbox verifies the link against the router identity before you rely on it. Every subscriber action from then on is pushed over that same RouterOS API connection.

For routers behind NAT or without a public IP, connect them through an encrypted WireGuard tunnel instead. ISPbox allocates the peer address from your pool, generates the keypair and an optional preshared key, and gives you ready-to-paste /interface wireguard commands - then manages the router over the tunnel with a 25-second keepalive.

Provision PPPoE and DHCP subscribers automatically

Choose how each router authenticates: PPPoE sessions backed by /ppp/secret entries and profiles, or static DHCP leases that bind a client MAC to its assigned IP. When you activate a service, ISPbox writes the matching configuration and address pool over the API; when you suspend or cancel it, ISPbox removes it again.

A first-time setup can build the groundwork for you - the ISPbox bridge, PPPoE server, per-pool profiles, and IP pools - so a fresh router is ready to take subscribers without manual RouterOS work.

Shape every client with simple queues

Speed limits come straight from your service packages. ISPbox creates a /queue/simple per client using the plan upload and download limits, tagged with an ISPBOX- service comment so plan changes and cleanups stay precise. Move a customer to a faster plan and the queue follows automatically.

RADIUS or direct API - your architecture, your call

Run a router in RADIUS mode and ISPbox registers it as a NAS (its public or WireGuard IP as the NAS name, with a shared secret), stores credentials for authentication, and sends bandwidth caps using the MikroTik Rate-Limit attribute. Prefer to skip RADIUS? Switch the router to API mode and ISPbox provisions sessions, leases, and queues directly. DHCP and PPPoE work with either.

Works with PPPoE & RADIUS, Network Monitoring, Provisioning

02 Why this feature matters

Built for high-speed ISP operations

Consolidate RouterOS Workflows

Manage service and subscriber operations with fewer handoffs between systems.

Improve Operational Clarity

Keep billing, support, and network actions tied to one shared context.

Reduce Manual Coordination

Give teams one source for execution and customer-facing outcomes.

Scale Reliable Processes

Support growth on MikroTik without increasing process complexity at the same pace.

03 Use cases

Where ISP teams put this to work

Run subscriber lifecycle workflows in MikroTik-heavy environments.
Support faster handoff between support and network teams.
Track customer-impacting actions with billing context.
Standardize daily operations across multiple sites.

// Related

What ISP and WISP teams search for

mikrotik isp billing mikrotik isp management mikrotik billing software mikrotik integration for wisp routeros billing system

04 FAQ

Frequently asked questions

Which MikroTik connection methods does ISPbox support?: ISPbox connects over the RouterOS API (default port 8728) using the router API username and password. For routers behind NAT or without a public IP, you can connect them through an encrypted WireGuard tunnel and manage them over that instead.
Do I need a RADIUS server to use MikroTik with ISPbox?: No. You can run each router in API mode, where ISPbox provisions PPPoE secrets, DHCP leases, and queues directly over the RouterOS API. If you prefer RADIUS, ISPbox registers the router as a NAS and pushes credentials and rate limits through it - both PPPoE and DHCP are supported either way.
How does ISPbox apply subscriber speed limits on MikroTik?: Speed limits come from the customer service package. In API mode ISPbox creates a MikroTik simple queue per client; in RADIUS mode it sends the MikroTik Rate-Limit attribute. When a customer changes plans, the limit updates automatically.
Does ISPbox support both PPPoE and DHCP on MikroTik?: Yes. Each router can run PPPoE (username and password sessions via /ppp/secret and profiles) or DHCP (static leases that bind a MAC to an IP). ISPbox can also run an initial setup that creates the bridge, PPPoE server, profiles, and address pools for you.
Do changes in the panel reach the router automatically?: Yes. Activating, suspending, or cancelling a service writes or removes the matching configuration on the router, so what you bill and what the network enforces stay in sync.