Free operator worksheet

FreeRADIUS readiness checklist

Review the evidence behind your ISP's RADIUS service before changing billing or access policy. Copy or print the checklist; no email or account is required.

Tick items here or print a blank copy. Ticks stay on this page until you reload; they are not saved or sent. Use Print / save PDF to keep your progress.

Record evidence before marking an item complete

Use this worksheet with the person who owns authentication, accounting and router access. A NAS (network access server) is the router or access device that sends RADIUS requests. Record pass, needs work or not applicable, an owner, and a dated evidence reference for each section. Keep passwords, shared secrets and subscriber data out of the worksheet.

These are operator checks for your existing system, not features that ISPAgents performs automatically. Rehearse failure and change scenarios with synthetic subscribers in an isolated lab before agreeing any production change window.

Review recordFill in
ScopeSites, NAS models/firmware, FreeRADIUS version and database dialect
OwnersAuthentication, database, network and recovery contacts
EvidenceRestricted log/test references, date and unresolved findings
DecisionStop conditions, approved next step and review date

1. NAS definitions, secrets and rotation

Check the FreeRADIUS 3.2 client configuration guidance against your installed release.

2. Accounting start, interim updates and stop

The FreeRADIUS accounting tutorial covers the packet flow; RFC 5080 discusses retransmission and duplicate handling.

3. Stale-session cleanup

FreeRADIUS simultaneous-use guidance explains why working accounting is a prerequisite.

4. SQL schema and permissions

Use the FreeRADIUS 3.x SQL guide as version-specific background, not a universal deployment recipe.

5. Backups and recovery

6. Redundancy and degraded operation

The FreeRADIUS module failover tutorial provides a lab exercise; your end-to-end failure tests must also cover the NAS and datastore.

7. Monitoring and response

8. CoA and disconnect

For a design using UDP 3799, verify the sender-to-NAS route, return traffic, configured listener and source-restricted firewall policy. Do not assume the RouterOS incoming default matches: it is documented as 1700 with acceptance disabled. Agree the port before a controlled lab test.

Consult RFC 5176 and the NAS vendor documentation, such as RouterOS RADIUS. Support and ports must be checked for your deployed version.

Review findings and ISPAgents scope

Unresolved secret exposure, unverified recovery or ambiguous session targeting should stop the related change. Assign each finding an owner and retest date. Use the router access audit checklist for the management path, and the migration checklist for a controlled handoff.

ISPAgents' existing FreeRADIUS integration is a guided pilot: a signed Status-Server probe exists; opt-in SQL accounting import has accepted proof. CoA/Disconnect drivers have fake-transport test coverage; real NAS mutation and end-to-end policy enforcement remain unqualified. SQL/API sync and policy write-back are not a complete integration. Managed RADIUS is also a guided pilot, requiring tenant-specific onboarding, live smoke testing and launch signoff. Completing this worksheet does not establish those product gates or authorize a cutover.

Optional: discuss your checklist findings with an operator.