Subscriber management · AAA drivers

AAA that fits your OSS — not the other way around.

Authentication, accounting and dynamic control run through pluggable drivers, selected independently in configuration. Authenticate against RADIUS or directly against your subscriber database; deliver accounting to RADIUS or straight into a cloud message bus. No middleware layer required.

The driver model

Auth and accounting selected independently

RADIUS

Full AAA against your existing RADIUS estate: PAP, CHAP and MS-CHAPv2 authentication, service selection by attribute, L2TP tunnel steering for LAC operation, Start/Interim/Stop accounting, and live session control via CoA and Disconnect.

RFC 2865/2866 · RFC 2868 · RFC 5176

shipping

Database

Authenticate directly against your subscriber database — no RADIUS layer in between. Credentials, service plan, addressing and VRF placement come straight from your schema (Microsoft SQL Server), so the billing system remains the single source of truth.

Direct SQL · plan & addressing from your schema

shipping

Service Bus

Accounting as structured JSON messages into Azure Service Bus — Start, Interim and Stop records delivered directly to your billing or data pipeline, with session, addressing and CGN context on every record. No log scraping, no batch imports.

Azure Service Bus · structured JSON records

shipping

Drivers combine freely: RADIUS end-to-end, database authentication with Service Bus accounting, or any other pairing. CGNAT session logging follows the same pattern, with syslog (RFC 5424 JSON) and Service Bus targets.

RADIUS in operation

Redundant servers · attribute-driven service

admin@lns1> show aaa radius

radius1.example.net auth · acct · Up · rtt 2.1 ms

radius2.example.net auth · acct · Up · rtt 2.4 ms

requests 1.2M · retransmit 0.01% · timeouts 0

coa listener enabled · RFC 5176 · authorised peers 2

Redundant RADIUS servers with live health, and the CoA listener for dynamic session control.

Service selection is attribute-driven: the service plan arrives with the Access-Accept, and RFC 2868 tunnel attributes steer L2TP LAC sessions to the correct wholesale endpoint — including tagged attribute groups with preference ordering, exactly as multi-homed wholesale designs expect.

Accounting interims carry traffic counters at the interval you configure, per NAS or per plan.

Dynamic control

CoA · Disconnect · applied without interruption

Change a subscriber's service in place: a CoA request re-provisions QoS, addressing or service plan on the live session, applied in the data plane without dropping the connection. Disconnect-Request terminates a session cleanly with a final accounting Stop.

Upgrades, suspensions and fair-use actions become API calls from your billing system rather than support tickets waiting for a reconnect.

admin@lns1> monitor aaa events

coa-request bob@example.net · plan gold-1g · from 192.0.2.50

coa-applied qos 1 Gbps / 200 Mbps · in 22 ms · session uninterrupted

acct-interim bob@example.net · in 4.2 GB · out 812 MB

A live plan change: CoA received, QoS re-provisioned in the data plane, session untouched.

Driver summary

All shipping

Driver	Role	Detail	Status
RADIUS	auth · acct · control	PAP/CHAP/MS-CHAPv2 · attribute-based service selection · RFC 2868 LAC tunnel steering · Start/Interim/Stop · RFC 5176 CoA/Disconnect	shipping
Database	auth	direct Microsoft SQL Server authentication · plan, addressing and VRF from your schema	shipping
Service Bus	acct	Azure Service Bus · structured JSON Start/Interim/Stop with session and CGN context	shipping
Syslog (CGN logging)	session logging	RFC 5424 JSON port-block events · sequence-numbered	shipping with CGNAT

BILLING PLATFORMS — the RADIUS driver interoperates with RADIUS-based ISP billing platforms; per-platform configuration guides are published with the documentation.

Point it at your AAA and test it.

Start free eval Download datasheet (PDF)