A new chapter. LiquidNAT is now part of LiquidWebSpace LTD. Meet the next era ↗
LIQUIDNAT RADIUS

Know the subscriber.
Connect the service.

Authentication is the beginning of the story. Bring identity, authorisation, accounting and operational context into the same conversation.

IDENTITY WITH PURPOSE

More than accept or reject.

01 /

Authentication

Understand subscriber identity, access method, client and realm. Distinguish a rejection from a timeout so the next action is clear.

02 /

Authorisation

Connect the subscriber to a defined service profile: addressing, speed, access policy and service state.

03 /

Accounting

Follow start, interim and stop events. Treat retries, duplicates and missing events as operational cases to reconcile.

04 /

Service changes

Plan package changes, suspension, restoration and CoA/disconnect behaviour with a clear view of session impact.

05 /

Integrated or external

Discuss the managed FreeRADIUS architecture or your existing RADIUS environment. Review attributes, dictionaries and server behaviour.

06 /

Client & realm context

Keep clients, realms, server groups and certificates visible in the service design. Separate identity policy from billing business logic.

JOIN THE DOTS

Make billing
and the edge agree.

Your billing system knows the commercial relationship. Your network needs precise service intent. Integration translates between them.

Activation to termination

Map create, suspend, restore, package change and terminate workflows to explicit, repeatable service actions.

Safe retries

Use stable identifiers, scoped credentials and idempotent operations in the integration design.

Keep the history

A terminated service and its accounting or required attribution history have different retention needs.

LESS FRICTION. MORE NETWORK.

Your next chapter
starts at the edge.

Talk through your network ↗