FreeRADIUS Integration for MikroTik Billing

WayaDesk / FreeRADIUS

FreeRADIUS integration introduces another service into the access path. The billing application, the RADIUS service and the router each have a role. A successful application installation does not prove that the complete authentication and accounting path is operating.

Identify the components

LinkDesk includes a separate RADIUS bridge and requires a configured Linux FreeRADIUS daemon for this deployment. Document where those components run and how the router reaches the service. Keep the public customer endpoint distinct from the administrative and authentication interfaces.

Define the evidence required

For one test subscriber, observe the request, the entitlement decision and the router’s result. Then verify accounting and expiry behaviour. This produces a useful record of the actual installation instead of assuming that a settings page labelled RADIUS establishes compatibility.

• Check successful and rejected authentication with controlled accounts.
• Confirm that accounting relates to the correct subscriber.
• Test behaviour when the required service is unavailable.

Keep supported policy separate from assumptions

The current implementation does not promise enforced RADIUS data quotas or strict global simultaneous-session control for RADIUS PPPoE. If these are mandatory, record them as unresolved requirements rather than assuming the external daemon makes them automatic.

Include the service in recovery

The operator’s restart and restore procedure must cover the bridge, daemon and router path. Assign responsibility for each component so that a future outage does not become a search for the person who originally installed it.