RADIUS can use TCP, but classic RADIUS normally uses UDP. In the traditional protocol, authentication and authorization messages use UDP port 1812, while accounting messages use UDP port 1813; newer RADIUS-related standards also define transport over TCP or TLS for specific deployments.
What RADIUS Does
RADIUS stands for Remote Authentication Dial-In User Service. It is a network protocol that lets a network access device—such as a wireless access point, VPN gateway, or switch—ask a central server whether a user or device should be allowed to connect. The server can also return authorization details, such as a network role or policy, and record accounting information about a session.
The network device is commonly called the RADIUS client or Network Access Server (NAS). It sends requests to a RADIUS server, which checks credentials or consults an identity system and replies with an acceptance, rejection, or challenge. The word “client” here means the network access device, not necessarily the end user’s computer.
Why Classic RADIUS Uses UDP
The original RADIUS design uses User Datagram Protocol (UDP), a connectionless transport. A sender can transmit a request without first establishing a transport connection, which suited early access networks and kept the protocol relatively simple. UDP itself does not guarantee delivery, ordering, or retransmission. RADIUS implementations therefore use request identifiers, authenticators, timers, and retransmissions to manage replies and recover from packet loss.
In the conventional port assignments, RADIUS authentication and authorization use UDP 1812, and accounting uses UDP 1813. Older deployments may use UDP 1645 for authentication and UDP 1646 for accounting, reflecting historical assignments. Administrators should check the actual server and device configuration rather than assume which ports are active.
- UDP 1812: commonly used for RADIUS authentication and authorization.
- UDP 1813: commonly used for RADIUS accounting, such as session start, interim, and stop records.
- TCP or TLS: available in newer RADIUS transport specifications and implementations, but not the default for every RADIUS deployment.
Does RADIUS Ever Use TCP?
Yes. RADIUS over TCP is defined in standards for carrying RADIUS messages over a reliable, connection-oriented transport. Related work also defines RADIUS over TLS (often called RadSec), which can protect the transport connection with TLS. These options are useful in some environments, including links where reliable stream transport or stronger transport-layer protection is required.
That does not mean that any RADIUS server automatically accepts TCP connections. The server and client must both support and be configured for the same transport, address, port, and security settings. A traditional RADIUS client sending UDP packets to a server configured only for TCP will not communicate successfully, and vice versa. TCP use is therefore a deployment choice, not a universal property of the protocol.
Also distinguish the RADIUS message format from its transport. RADIUS is the application-layer protocol; UDP, TCP, and TLS describe how messages are carried across the network. A port number alone does not prove that a service is using a particular transport: UDP 1812 and TCP 1812 are separate endpoints.
How a RADIUS Exchange Works
For a typical Wi-Fi login, the access point or controller acts as the RADIUS client. It receives authentication information through the network access process and sends a RADIUS request to the configured server. The server checks the request and sends a response, such as Access-Accept, Access-Reject, or Access-Challenge. The access device then applies the response to the connection.
With UDP, the exchange is request-and-response without a persistent transport connection for each message. If a reply does not arrive before a timeout, the client may retransmit the request. RADIUS identifiers help match replies to requests. Accounting uses separate request types to report session events; it is not the same thing as authentication, even though both are handled by RADIUS.
With TCP, the transport establishes a connection and provides ordered, reliable delivery of bytes. RADIUS messages still need to be framed and interpreted according to the applicable transport specification. Reliability at the TCP layer does not replace the need for RADIUS-level authentication, authorization decisions, or appropriate protection of credentials and attributes.
Choosing and Configuring a Transport
Use the transport that the RADIUS client and server both support and that fits the network’s security and reliability requirements. For many established networks, UDP remains the ordinary choice. A move to TCP or TLS should be planned as an interoperable configuration change, not as a simple port substitution.
- Confirm supported transports and ports in both products’ documentation and configuration.
- Permit the selected protocol and port through firewalls in both directions as required by the implementation.
- Configure matching shared-secret or certificate settings. A shared secret is used by traditional RADIUS mechanisms; TLS deployments additionally require correct certificate and trust configuration.
- Check whether accounting is enabled separately and whether it uses the intended transport and port.
- Test authentication, rejection, challenge, and accounting behavior, and review server and client logs.
Do not assume TCP is inherently encrypted. TCP provides reliable delivery, not confidentiality. Likewise, do not assume that using a familiar port makes a connection secure. Protection depends on the RADIUS method, transport, credential handling, and configuration. Where sensitive traffic crosses an untrusted network, use a properly supported protected transport and follow the organization’s security requirements.
Common Connectivity Problems
A frequent issue is opening the correct port number for the wrong protocol—for example, permitting TCP 1812 when the configured client sends UDP 1812. Firewall rules distinguish TCP from UDP, so both the protocol and port must match. Another common problem is a mismatch between the client’s destination port and the server’s listening port.
- No response: check routing, firewall rules, server status, destination address, and UDP-versus-TCP configuration.
- Requests arrive but are rejected: check the shared secret, client identity, authentication method, and server policy.
- Authentication works but records are missing: check accounting configuration and the accounting port, commonly UDP 1813 in classic deployments.
- Intermittent failures: inspect packet loss, timeouts, retransmissions, server load, and any network device handling the traffic.
Packet captures can help identify whether packets are being sent and whether replies return, but encrypted transport changes what their contents reveal. Logs from both ends are often needed to tell a transport failure from an authentication or policy rejection.
Frequently Asked Questions
What port does RADIUS use?
Classic RADIUS commonly uses UDP 1812 for authentication and authorization and UDP 1813 for accounting. Older configurations may use UDP 1645 and 1646. TCP-based or TLS-based deployments may use different configured ports, so verify the implementation.
Is RADIUS UDP or TCP?
Traditional RADIUS is primarily associated with UDP. TCP and TLS transports are also defined and supported in some newer implementations, but must be configured at both ends.
Can I use TCP port 1812 for RADIUS?
Only if the RADIUS client and server support and are configured for RADIUS over TCP on that port. TCP 1812 is not interchangeable with the conventional UDP 1812 service.
Is RADIUS over UDP secure?
UDP does not provide encryption or security by itself. Traditional RADIUS has protocol-specific protections, but these should not be mistaken for full encryption of all attributes. For traffic over untrusted networks, consider a supported TLS-based transport and configure it correctly.
Does RADIUS accounting use the same port as authentication?
Usually not in classic deployments: authentication and authorization commonly use UDP 1812, while accounting commonly uses UDP 1813. Implementations can be configured differently, so check the settings on both systems.
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