RADIUS and AAA
RADIUS for ISPs: FreeRADIUS, PPPoE, Accounting & CoA
Centralize subscriber authentication, authorization and accounting while keeping plan, payment and support context connected. ISPbills provides a FreeRADIUS operating interface for NAS devices, attributes, sessions and controlled subscriber lifecycle actions.
Inspect the working interface, then verify your exact environment.
This is a real ISPbills product capture, not a conceptual mockup. Interface access depends on role and configuration; integration behavior must be tested with the actual provider, device model, firmware and network path.
AAA policy should follow an explicit subscriber and service record.
RADIUS decides whether access is allowed and records how a session behaves. Billing decides whether the account is commercially eligible. Joining those states reduces manual mismatches while retaining an audit trail for operators.
Register each NAS
Store the client address, shared-secret relationship and device context with appropriate access controls.
Map subscriber credentials
Relate username, package and service state to the required check and reply attributes.
Authenticate and authorize
Evaluate credentials and return policy appropriate to the subscriber and access service.
Account and control sessions
Retain start, interim and stop records, then use supported CoA or disconnect workflows when required.
Capabilities connected to the operating workflow
Use these as evaluation areas, then confirm the exact device, provider, version and commercial requirements that apply to your deployment.
FreeRADIUS management
Operate NAS records, subscriber attributes and policy from the ISPbills administration interface.
PPPoE authentication
Centralize credentials and plan policy for supported broadband access servers.
Hotspot AAA
Use centralized identity and session accounting across compatible hotspot infrastructure.
Accounting records
Review session start, interim updates, stop state, usage and termination context.
CoA and disconnect
Coordinate supported session changes when commercial or package state changes.
Operational diagnosis
Put failed authentication, active sessions and subscriber billing state in one investigation path.
Explore this topic in depth
Each page owns a distinct search and implementation question, with direct links into current documentation.
ISP RADIUS Architecture and Deployment Guide
Design a centralized ISP RADIUS architecture for authentication, authorization, accounting, NAS policy, redundancy and operational diagnosis.
Read focused guideFreeRADIUS ISP Billing and Subscriber Management
Connect FreeRADIUS authentication and accounting to ISP subscriber packages, payment state, sessions and support workflows.
Read focused guideMikroTik FreeRADIUS Integration for ISP Networks
Configure and validate MikroTik as a FreeRADIUS NAS for PPPoE or Hotspot authentication, accounting and session control.
Read focused guidePPPoE RADIUS Authentication and Billing
Connect PPPoE RADIUS authentication, plan authorization, session accounting and billing eligibility for ISP subscribers.
Read focused guideRADIUS Accounting for ISP Subscriber Sessions
Understand RADIUS start, interim and stop records, session state, usage visibility and reconciliation for ISP access networks.
Read focused guideRADIUS CoA and Disconnect for ISP Sessions
Plan RADIUS Change of Authorization and disconnect workflows for package updates, suspension and controlled subscriber session changes.
Read focused guideRADIUS Hotspot Authentication and Accounting
Centralize Hotspot users, plan authorization, session accounting, vouchers and subscriber state with RADIUS and ISPbills.
Read focused guideISP RADIUS Server and Subscriber AAA
Evaluate ISP RADIUS for centralized authentication, authorization, accounting, subscriber policy, NAS management and session control.
Read focused guideTreat RADIUS as production infrastructure, not a checkbox.
Confirm the current product behavior in a representative environment. Public pages describe the operating model; implementation documentation and a controlled pilot establish the exact fit.
- Network pathValidate UDP reachability, source addresses, shared secrets, time synchronization and firewall rules.
- Attribute contractDocument vendor dictionaries, check and reply attributes, interim intervals and required policy behavior.
- Failure designPlan redundancy, logging, retry behavior and the expected customer experience when AAA dependencies are unavailable.
Product, evidence and implementation paths
Answers for evaluation and implementation
What does RADIUS do for an ISP?
RADIUS centralizes authentication, authorization and accounting for compatible access equipment. It can validate credentials, return service attributes and record session activity.
Does RADIUS generate invoices?
No. RADIUS is an AAA protocol, not an invoicing engine. ISPbills connects RADIUS access state to a separate subscriber billing lifecycle.
What is RADIUS accounting?
RADIUS accounting receives session start, interim and stop records from a NAS. These records help operators inspect connection time, usage and termination context.
Does ISPbills support RADIUS CoA?
ISPbills supports configured CoA and session-control workflows for compatible devices. Exact vendor behavior should be validated in a representative pilot.
Bring the devices, billing rules and integrations your ISP actually uses.
Use the online workspace for product exploration, or ask the team to scope migration and compatibility questions.