Router-Local Accounts or RADIUS: What Changes?

WayaDesk / FreeRADIUS

Local accounts and RADIUS-based access place policy decisions in different parts of the installation. Compare the operating responsibility and failure paths, not just the names of the supported protocols.

Map where decisions happen

In a router-local workflow, relevant account information is applied to the router. A RADIUS workflow introduces a separate authentication service and its communication path. Write down which component must be available when a customer attempts to connect.

Check what staff can observe

The evidence used for a local account may differ from the evidence available through accounting. Staff need to know which timestamps and states they are reading. A stale record in one layer should not be treated as a definitive live observation from another.

• List the components needed for a new login.
• Compare supported limits for the exact service type.
• Include each component in the restart and backup plan.

Use an interruption exercise

During an agreed pilot, examine what happens when the policy service or router path is unavailable. Record actual behaviour rather than assuming an outage will either preserve or terminate every session. The answer can depend on the deployed configuration and existing sessions.

Choose what you can maintain

Additional centralisation may suit an operator’s requirements, but it also adds administration. Decide who will maintain the daemon, credentials and host. A simpler operating arrangement can be preferable when it satisfies the required policies and the team can support it reliably.