Protocol ExplorerGuidesPricing

RADIUS Protocol: Access Requests and Responses

RADIUS carries network access decisions between an access device and an authentication service. Read the request, response code and attributes without confusing the network access server with the end user.

Updated · Editorial approach and simulation limits

The RADIUS client is usually the access device

RADIUS centralizes authentication, authorization and configuration for network access. The client in the protocol exchange is commonly a Network Access Server such as a VPN gateway, wireless controller or switch. The person trying to connect is the user whose credentials or identity the NAS presents; that person is not automatically the RADIUS client.

The NAS receives an access attempt, gathers the information required by its policy, and sends a RADIUS packet to a configured server. The server evaluates the request and returns a decision or asks for more information. This separation lets an organization apply shared policy across many access devices.

RADIUS is a client-server protocol, not the browser login page itself. A hotel portal, enterprise Wi-Fi authentication, remote-access VPN and wired 802.1X port can all involve different user interfaces while relying on a RADIUS exchange behind the access device.

Access-Request, Access-Challenge, Accept and Reject

An Access-Request asks the server to evaluate a network access attempt. The server can return Access-Accept to authorize access, Access-Reject to deny it, or Access-Challenge when another exchange is needed before a final decision. These response codes are not interchangeable, and a challenge is not yet an acceptance.

For an Access-Challenge flow, the NAS relays the server’s challenge to the user or supplicant, receives the next response, and sends a follow-up request. A State attribute can carry server context across that exchange. When reading a trace, match the request and response identifier and follow the conversation until it reaches a final result.

An Accept can carry attributes that influence the session, such as a service type, assigned network parameters, session limits or VLAN-related information where the deployment supports them. A Reject means this request was not authorized; it does not by itself explain whether the cause was a bad password, policy, account state or a backend dependency.

Attributes explain the context of a decision

RADIUS packets contain a header followed by typed attributes. The code tells you what kind of message it is; the identifier helps correlate a response; the length bounds the packet; and the attributes carry the user name, NAS identity, requested service, authentication material or decision data defined by the applicable specifications.

Useful attributes depend on the access method. A network device can identify itself with NAS-IP-Address or NAS-Identifier, while a user-facing identity may appear separately. In an EAP deployment, RFC 3579 defines how EAP messages are carried in RADIUS. Not every RADIUS exchange uses EAP, and an attribute’s presence should be interpreted in the context of the deployment.

Do not infer the authorization result from a single attribute. Compare the complete request and response, the NAS configuration and the relevant server policy. In a capture across a protected transport, some or all RADIUS content may be encrypted and visible only at the endpoints.

Authentication, authorization and accounting are related jobs

Authentication asks whether the presented identity can be verified. Authorization decides what the accepted session may do. Accounting records session events such as start, interim update and stop. They are often integrated operationally, but they are different questions and may use separate RADIUS message types or services.

The original RADIUS specification assigns UDP port 1812 for authentication and authorization. RADIUS Accounting is specified separately, with the conventional UDP port 1813. Port numbers are clues, not proof: deployments can use other ports, proxies, or protected transports, so read the observed configuration rather than assuming every packet follows the default.

Accounting records help operators reconcile an accepted session with a later disconnect or usage report. They do not replace the real-time Access-Accept or Access-Reject decision.

How RADIUS fits an enterprise Wi-Fi exchange

In an 802.1X wireless network, the access point or controller acts as the authenticator and RADIUS client, while a supplicant on the device participates in the EAP method. The NAS forwards EAP exchanges to the server using the RADIUS mechanisms described in RFC 3579. The server’s result is then used by the authenticator to control network access.

A trace can therefore contain several distinct conversations: 802.11 association, EAP over the local link, RADIUS between the access device and server, and later DHCP or DNS traffic after access is granted. A missing DHCP lease may be downstream of a failed RADIUS decision, but it is not itself a RADIUS error.

For a public Wi-Fi portal, the flow can instead involve a web form and a server-side update to access policy. That architecture may use RADIUS as one backend component, but the portal itself is not synonymous with RADIUS.

Transport security: classic RADIUS and RADIUS/1.1

The original RFC 2865 protocol is commonly deployed over UDP with a shared secret and legacy packet-protection mechanisms. Operators should not mistake those mechanisms for end-to-end encryption of every attribute or for modern TLS transport. Protect the path and secrets according to current deployment guidance.

RADIUS/1.1 is a newer transport profile defined experimentally in RFC 9765. It uses ALPN to negotiate a profile over TLS or DTLS, requires TLS 1.3 or later, and removes the legacy MD5-based packet authentication and attribute obfuscation from that profile. RFC 9765 updates several RADIUS documents but does not change the RADIUS packet and attribute formats.

RADIUS/1.1 support is not implied by a server speaking RADIUS or by a successful UDP exchange. Confirm that both peers support and negotiate the profile. The interactive lesson presents the classic request-response model; it is not a wire capture of a particular vendor’s current security configuration.

A practical checklist for reading a RADIUS trace

Start by identifying the client and server addresses and transport. Group packets by the RADIUS identifier and inspect the code sequence. For a simple exchange, expect an Access-Request followed by one of the decision responses. For a challenge, trace the additional round trips before calling the result final.

Check packet length and attribute boundaries before interpreting values. Correlate the NAS identity with the device you expect to be the client, then compare the user identity, service type and EAP attributes only where visible and authorized. Retransmissions may indicate a lost response or timeout; a repeated request is not automatically a second user attempt.

Finally, line up the RADIUS timeline with access-device logs and the user-visible result. If the server accepted the request but the client receives no address, inspect the NAS policy and DHCP path next. If the server rejected it, use the server’s policy logs to find the reason rather than guessing from the packet code.

What the RADIUS animation simplifies

The Protocol Explorer RADIUS overview focuses on the decision exchange so the message roles are visible. Real deployments can add EAP methods, proxies, accounting, vendor-specific attributes, retransmission timers, protected transports and local policy. The sequence shown is a learning model, not a live authentication attempt.

For implementation requirements, use the cited RFCs and the vendor or operator configuration that applies to the network under review. Do not place real credentials, shared secrets or subscriber identifiers into a public packet trace.

Explore RADIUS interactively

Open the matching lesson to follow the exchange packet by packet. This is a scripted learning model with illustrative timing, not a capture of your network. The overview is free; the full lesson is included with the one-time Pro pass.

Open the RADIUS animation · Compare Free and Pro

Standards and primary sources

Use these specifications for authoritative protocol requirements. The lesson summarizes selected behaviors and does not replace the source documents.

Related protocol lessons

Browse all security and access protocols ·

  • How a network login flow fits together