01 Feature Spotlight

PPPoE + RADIUS Workflows Connected to Billing

Handle subscriber access logic and revenue workflows together, so provisioning and billing remain synchronized.

  • Subscriber access workflows mapped to account status
  • Centralized visibility for PPPoE and billing context
  • Cleaner operations for support and NOC teams
PPPoE and RADIUS billing workflow dashboard
→ Under the hood

How ISPbox runs PPPoE and RADIUS

Keep subscriber access and billing in lockstep. Whether you authenticate PPPoE sessions through a RADIUS server or provision them straight over the RouterOS API, ISPbox manages the credentials, IP assignment and speed limits, and changes them automatically as a customer is activated, suspended for non payment, or restored.

RADIUS the way MikroTik expects it

ISPbox registers each router as a RADIUS NAS using its public or WireGuard IP and a shared secret, stores subscriber credentials for authentication, assigns a fixed Framed IP where needed, and sends bandwidth caps using the Mikrotik-Rate-Limit attribute. FreeRADIUS is reloaded automatically after changes.

Or skip RADIUS and use the API

Prefer not to run a RADIUS server? Put the router in API mode and ISPbox writes the PPP secret, profile and an upload and download simple queue directly over the RouterOS API. Either path keeps the panel as the single source of truth for who can connect and how fast.

Access follows billing automatically

When an invoice goes past due and grace, ISPbox can block the subscriber by removing the secret or RADIUS entry, or limit them to a reduced speed, then restore full service the moment the payment lands. No manual queue edits, no forgotten reactivations.

Works with MikroTik Integration, Provisioning, Billing

02 Why this feature matters

Built for high-speed ISP operations

Keep Access and Billing Aligned

Reduce mismatches between subscriber status and billing state.

Respond Faster to Account Issues

Support teams get one place to review service and billing context.

Simplify Subscriber Operations

Use one operational model for account handling and revenue processes.

Scale PPPoE/RADIUS Management

Maintain process consistency as subscriber volume increases.

03 Use cases

Where ISP teams put this to work

  • Run PPPoE subscriber workflows tied to billing state.
  • Handle RADIUS-linked account operations with fewer manual steps.
  • Resolve suspended/reactivated account questions faster.
  • Support growth without splitting provisioning and billing data.
// Related

What ISP and WISP teams search for

pppoe billing software radius billing software isp radius server billing wisp pppoe management radius subscriber management
04 FAQ

Frequently asked questions

Do I have to use RADIUS for PPPoE?
No. You can authenticate PPPoE through a RADIUS server, where ISPbox registers the router as a NAS and pushes credentials and rate limits, or provision PPP secrets and profiles directly over the RouterOS API. Both keep billing in sync.
How are speed limits enforced?
In RADIUS mode ISPbox sends the Mikrotik-Rate-Limit attribute; in API mode it creates a per client simple queue from the service package. Plan changes update the limit automatically.
What happens when a customer does not pay?
After the due date plus your grace period, ISPbox can block the subscriber or rate limit them to a reduced speed, then restore full access automatically when the invoice is paid.
Can I assign static IPs to subscribers?
Yes. ISPbox can assign a fixed address to a PPPoE subscriber, as a Framed IP in RADIUS mode or the remote address on the PPP secret in API mode.

Running PPPoE and RADIUS at Scale?

Use ISPbox to align subscriber access workflows with billing operations.