Router RADIUS configuration connects a router to a Remote Authentication Dial-In User Service (RADIUS) server so the server can authenticate network users and, when supported, authorize access and record activity. The exact settings depend on the router and server; typically, you specify the server address, authentication port, shared secret, and the network access method that will use RADIUS.
What RADIUS Does
RADIUS is a client-server protocol commonly used for centralized network access control. In this arrangement, the router or wireless access point acts as a RADIUS client (also called a network access server), while a separate server checks credentials against an account store or policy. RADIUS is not itself a router feature for improving signal or assigning Wi-Fi coverage; it is an authentication and accounting service.
A typical exchange works like this: a user or device attempts to connect, the router sends an authentication request to the configured server, and the server responds with acceptance, rejection, or a request for additional information. If access is accepted, the server may provide policy attributes, such as a VLAN assignment, depending on the equipment and configuration. Accounting records can track session start, stop, or usage when both ends support and enable accounting.
Settings You Usually Need
Before opening the router’s administration interface, collect the settings from the RADIUS administrator. Do not assume that common defaults apply: ports, security requirements, and supported authentication methods vary by product and deployment.
- Server address: The RADIUS server’s IP address or hostname. A hostname requires working DNS resolution from the router.
- Authentication port: The UDP destination port used for access requests. UDP 1812 is the current conventional port; older installations may use UDP 1645.
- Accounting port: If accounting is used, UDP 1813 is conventional; older deployments may use UDP 1646. Accounting can often be enabled separately from authentication.
- Shared secret: A secret configured identically on the router and server. It is not the user’s Wi-Fi password, and a mismatch prevents successful communication.
- Authentication method and identity settings: For example, WPA2-Enterprise or WPA3-Enterprise for Wi-Fi, along with the EAP method and certificate requirements set by the network.
- Timeout and retry settings: These control how long the router waits and whether it resends requests. Use values recommended by the administrator rather than increasing them blindly.
Some products also ask for a source interface or source IP address. This determines which address the router uses when contacting the server. The server must recognize that address as an authorized RADIUS client; a router with several interfaces may otherwise send requests from an unexpected address.
How to Configure It
Menu names differ across router firmware, but the general sequence is consistent. Make changes during a period when a failed login will not lock out essential users, and keep an existing administrator connection available if possible.
- Confirm that the router can reach the RADIUS server over the intended network path. Check routing, DNS if using a hostname, and firewall rules for the required UDP traffic.
- Open the router’s administration interface and find the authentication, enterprise Wi-Fi, access control, or RADIUS settings.
- Add the server address, authentication port, and shared secret. Add the accounting server and port only if accounting is part of the design.
- Choose the access service to protect, such as an enterprise wireless network or supported VPN access, and configure its compatible authentication method.
- Save the settings, then test with an authorized test account or device. Confirm both a successful login and a rejected attempt, and review router and server logs.
For enterprise Wi-Fi, configuring the router is only one part of the setup. Client devices must also use compatible security and EAP settings. With certificate-based EAP, clients need to validate the correct server certificate; users should not be told to bypass certificate warnings as a workaround.
Common Problems and Troubleshooting
When authentication fails, first determine whether the router can reach the server and whether the server receives the request. Router status pages, RADIUS logs, and firewall logs help distinguish a network failure from a credential or policy rejection.
- No request reaches the server: Check the server address, route, DNS, firewall, UDP port, and the router’s selected source interface.
- The server reports an unknown client: Register the router’s actual source IP address on the RADIUS server. A changed WAN or LAN address can make an existing client entry incorrect.
- Requests arrive but are rejected: Check the account, access policy, EAP method, certificate trust, and any required group or device conditions.
- Shared-secret or authenticator errors: Carefully compare the secret at both ends. Avoid pasting extra spaces or using a different value on one server node.
- Intermittent delays: Investigate packet loss, server load, redundant-server settings, and timeouts. Simply increasing retries can slow down failures without fixing their cause.
A common misconception is that a successful ping proves RADIUS is working. Ping tests basic IP reachability, not whether the relevant UDP request reaches the right service, whether the shared secret matches, or whether the server’s policy accepts the user.
Security and Maintenance
Treat the shared secret as a credential: use a strong, unique value, restrict who can view or change it, and replace it if it may have been exposed. Use protected management access for the router and restrict which systems can send requests to the RADIUS server. RADIUS over ordinary UDP does not encrypt every part of an authentication exchange; select a suitable EAP method and protect the surrounding network according to the organization’s security requirements. RadSec, which carries RADIUS over TLS, is an option only when both the router and server support it.
Keep router and server software maintained, monitor authentication logs, and document the server addresses, ports, client addresses, and responsible administrator. If the server is unavailable, decide in advance whether access should fail closed or use a carefully controlled fallback. A fallback can preserve connectivity, but may weaken the access policy if it is broader than intended.
Frequently Asked Questions
What port does a router use for RADIUS?
UDP 1812 is the conventional authentication port and UDP 1813 is the conventional accounting port. Older configurations may use 1645 and 1646. Use the ports configured on the server and allowed by the network firewall.
Is a RADIUS shared secret the same as the Wi-Fi password?
No. The shared secret is used between the router and RADIUS server to protect and validate their protocol exchange. A user’s credentials or enterprise Wi-Fi authentication are separate.
Can I use RADIUS with a home router?
Only if the router or access point supports RADIUS client configuration and the relevant enterprise authentication feature. Many consumer routers do not provide those controls; check the device’s documentation.
Why does RADIUS work on one access point but not another?
The server may recognize one access point’s source address but not the other’s, or the devices may have different secrets, ports, EAP settings, routes, or firmware behavior. Compare server logs and each client’s configuration.
Does RADIUS encrypt Wi-Fi traffic?
RADIUS handles authentication and related access information; the Wi-Fi security protocol protects the wireless connection. Enterprise Wi-Fi uses both, and they must be configured compatibly.
When RADIUS Is Useful
RADIUS is most useful when an organization needs centrally managed access across multiple routers or access points, individual accounts instead of one shared network password, or policy and session accounting. For a small network with no need for centralized identity management, a simpler personal Wi-Fi security mode may be easier to maintain. The right configuration is the one supported by the equipment and aligned with the network’s authentication, certificate, and access policies.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this section
- Skip Calculator for Soil: What It Can and Can’t Do7.500 m³
- USD to KPW Calculator: Convert Dollars to North Korean Won90,000.00 KPW
- OK Calculator on TV on the Radio? Meaning Explained
- Pension Calculator KP: Estimate Your Pension Benefits
- Neonatal Kp Calculator: What It Means80.0000 mmol/mmol
- Newton to kp Converter Calculator and Formula1.0000 kp