bitlvl
EN

Port 513 rlogin / who · TCP and UDP

rlogin (TCP) and who (UDP): the BSD "r" commands, which trusted the client's claimed username and host.

Port513
TransportTCP and UDP
Servicerlogin / who — BSD r-commands; obsolete
CategoryLegacy services
Rangewell-known (0–1023, needs root to bind on Unix)
EncryptedNo, plaintext
ExposureDisable it

What runs on port 513

rlogin (TCP) and who (UDP): the BSD "r" commands, which trusted the client's claimed username and host. Replaced by SSH in the 1990s; appears today only on very old Unix systems and in nmap output.

Software that uses it: rlogind (historical)

Should port 513 be open?

Disable it. This is a legacy or insecure protocol. The recommendation is not to firewall it but to turn the service off and use the modern replacement.

Check port 513

# on the host: is anything listening, and which process?
ss -ltnp 'sport = :513'
ss -lunp 'sport = :513'
sudo lsof -i :513

# from another machine: is it reachable?
nc -zv host 513
nmap -p 513 host
nc -zuv host 513
sudo nmap -sU -p 513 host
curl -v telnet://host:513      # raw TCP connect test, Ctrl-C to leave

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 513

# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 513 proto tcp
sudo ufw allow from 10.0.0.0/8 to any port 513 proto udp
sudo ufw deny 513/tcp
sudo ufw deny 513/udp

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 meta l4proto { tcp, udp } th dport 513 accept
nft add rule inet filter input meta l4proto { tcp, udp } th dport 513 drop

# iptables (legacy)
iptables -A INPUT -p tcp --dport 513 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 513 -j DROP
iptables -A INPUT -p udp --dport 513 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p udp --dport 513 -j DROP

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=513 protocol=tcp accept'

Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 513" 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 513 TCP or UDP?

Both. rlogin / who uses TCP and UDP on 513: BSD r-commands; obsolete.

Is port 513 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 513 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 513 and which process. From another machine, nc -zv host 513 or nmap -p 513 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).

Can rlogin / who 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.