FreeRADIUS Pilot Acceptance Checklist

WayaDesk / FreeRADIUS

A useful RADIUS pilot proves the complete path on the intended network. The outcome should be a short evidence record that another operator can understand, rather than a statement that the service started without an error.

Begin with known accounts

Prepare a valid test subscriber, an expired account and a deliberately restricted case. Document their expected outcomes before testing. Use the router and customer equipment intended for deployment so the result is relevant to the operating environment.

Check decisions and observations

Verify authorised authentication, rejection where required, accounting association and the effect of renewal or expiry. If the operator depends on a particular limit, demonstrate that exact limit rather than inferring it from another feature.

• Record the component versions and non-secret deployment layout.
• Capture expected and observed results for each test account.
• Repeat the relevant checks after a controlled service restart.

Include an interruption

Examine the behaviour when the bridge, daemon or required network path becomes unavailable. Do not assume the result for existing sessions or later logins. Record the actual behaviour and the recovery process that staff will use.

Decide whether to proceed

List unresolved issues and the person responsible for each. Keep unsupported requirements, such as the current global RADIUS PPPoE simultaneous-session limitation, visible. Accept the pilot only when the required service behaviour has been demonstrated and the business understands the remaining scope.