| Port | 1812 |
|---|---|
| Transport | UDP |
| Service | RADIUS auth |
| Category | Authentication and directories |
| Range | registered (1024–49151) |
| Encrypted | No, plaintext |
| Exposure | Private network or VPN only |
Port 1812 RADIUS auth · UDP
RADIUS authentication: the protocol behind WPA2/WPA3-Enterprise Wi-Fi (802.1X), VPN logins, switch port authentication and ISP subscriber authentication.
What runs on port 1812
RADIUS authentication: the protocol behind WPA2/WPA3-Enterprise Wi-Fi (802.1X), VPN logins, switch port authentication and ISP subscriber authentication. Only the password is obfuscated with the shared secret; everything else is plaintext, so RADIUS traffic stays on the management network or inside RadSec (TLS, port 2083). Old servers used 1645.
Software that uses it: FreeRADIUS · Microsoft NPS · Cisco ISE · Aruba ClearPass · Okta/JumpCloud RADIUS
Should port 1812 be open?
Private network or VPN only. Nothing good comes from this port being reachable from the internet. Keep it on an internal network, reach it over a VPN or an SSH tunnel, and firewall it from everything that does not need it.
- radtest user pass server 0 secret is the quickest end-to-end check.
- A wrong shared secret shows up as "Received packet from X with invalid Message-Authenticator" on the server.
Check port 1812
# on the host: is anything listening, and which process? ss -lunp 'sport = :1812' sudo lsof -i :1812 # from another machine: is it reachable? nc -zuv host 1812 sudo nmap -sU -p 1812 host
A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.
Allow or block port 1812
# ufw (Ubuntu/Debian) sudo ufw allow from 10.0.0.0/8 to any port 1812 proto udp sudo ufw deny 1812/udp # nftables nft add rule inet filter input ip saddr 10.0.0.0/8 udp dport 1812 accept nft add rule inet filter input udp dport 1812 drop # iptables (legacy) iptables -A INPUT -p udp --dport 1812 -s 10.0.0.0/8 -j ACCEPT iptables -A INPUT -p udp --dport 1812 -j DROP # firewalld sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=1812 protocol=udp accept'
Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 1812" with no source is just "open".
Related ports
Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.
Questions
Is port 1812 TCP or UDP?
UDP. RADIUS auth is datagram-based; TCP 1812 is not used by it.
Is port 1812 encrypted?
No, plaintext. Anything sent over it can be read by whoever is on the path, so it belongs on a trusted network or inside a VPN or SSH tunnel.
How do I check whether port 1812 is open?
On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 1812 and which process. From another machine, nc -zv host 1812 -u or nmap -p 1812 -sU host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).
Can RADIUS auth run on a different port?
Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.