RADIUS Ports Explained: 1812, 1813, 1645, 1646 and 3799 (UDP vs TCP)


Which ports does RADIUS actually use, and why do so many deployments get one of them wrong? Our latest guide, RADIUS Ports Explained: 1812, 1813, 1645, 1646 and 3799 (UDP vs TCP), is a practical reference for NOC engineers, architects and security teams at ISPs, carriers and cable operators.

The ports at a glance

  • UDP 1812: authentication and authorization, from NAS to AAA server

  • UDP 1813: accounting, which feeds billing and usage records

  • UDP 3799: CoA and Disconnect, sent from the AAA or policy server back to the NAS

  • TCP 2083: RadSec (RADIUS over TLS)

  • 1645 and 1646: the legacy pre-standard pair that some older equipment still defaults to

The rule most firewalls miss

Port 3799 runs in the opposite direction to everything else. Firewall rules written for authentication and accounting assume the NAS starts every exchange, so CoA requests get dropped. Logins keep working, and the problem only surfaces when a policy change or disconnect fails to reach a subscriber.

UDP, TCP and the move to TLS

The article explains why RADIUS uses UDP, how retransmissions and failover work, and where RADIUS over TCP fits. It also covers the IETF’s July 2026 draft proposing to retire RADIUS over UDP and TCP outside secure networks, and the 2024 BlastRADIUS vulnerability that added urgency. Its advice is to enforce Message-Authenticator now and start planning RadSec.

 

Comments

Popular posts from this blog

The advantages of 5G service-based architecture (SBA)

Implementation Considerations: Navigating the AI Agent Assist Journey — Part III

How telcos can redefine CX with a zero-touch network strategy